Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add benchmarking to local dev and to CI/CD #100

Merged
merged 19 commits into from
Sep 2, 2023
Prev Previous commit
Next Next commit
Copy edit
dqii committed Sep 1, 2023
commit 3fed4dff3c02680fdc51ded25cbcdaeb8c66510e
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -26,8 +26,7 @@ make benchmark-print-only
## VSCode and IntelliSense

`.vscode/c_cpp_properties` is configured to use `./build/compile_commands.json`.
If you build lanterndb in a different directory, make sure to update `.vscode` config appropriately
in order to have IntelliSense working.
If you build lanterndb in a different directory, make sure to update `.vscode` config appropriately in order to have IntelliSense working.

## Debugging the C codebase

@@ -41,6 +40,7 @@ Below is a short recording demonstrating the use of `livedebug.py`:
When modifying the SQL interface, you add relevant SQL logic under `sql/`. In addition, you add an update script under `sql/updates`, in a file named `[CURRENT_VERSION]--latest.sql`. You should create this file if it does not exist.

Note that you never modify an already existing update file that does not have `latest` in its name.

The files that do not have `latest` in the name are part of a previous releases and help LanternDB users update to a newer version of the extension via `ALTER EXTENSION lanterndb UPDATE`.

## Browsing the Postgres repository offline