Skip to content

ci: add pg12, pg13 test #26

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jan 28, 2023
Merged

ci: add pg12, pg13 test #26

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/integration_tests.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,10 @@ jobs:
strategy:
fail-fast: false
matrix:
psql_version: ['14.4', '15.1']
psql_version: ['12.13', '13.9', '14.4', '15.1']
python_version: ['3.8', '3.9', '3.10']

name: Integration test for PostgreSQL ${{ matrix.psql_version }} and Python ${{ matrix.python_version }}
name: PostgreSQL ${{ matrix.psql_version }} and Python ${{ matrix.python_version }} integration test
runs-on: ubuntu-latest

steps:
Expand Down Expand Up @@ -83,4 +83,4 @@ jobs:
run: sudo pg_lock_tracer -x ~/postgresql/bin/${{ matrix.psql_version }}/bin/postgres -v -p $(pidof postgres) --statistics --dry-run

- name: Check that pg_lw_lock_tracer can be executed
run: sudo pg_lw_lock_tracer -p $(pidof postgres) --dry-run
run: sudo pg_lw_lock_tracer -p $(pidof postgres) --dry-run
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -767,7 +767,7 @@ pip install git+https://github.com/jnidzwetzki/pg-lock-tracer
```

## PostgreSQL Build
The software is tested with PostgreSQL 14 and PostgreSQL 15. In order to be able to attach the _uprobes_ to the functions, they should not to be optimized away (e.g., inlined) during the compilation of PostgreSQL. Otherwise errors like `Unable to locate function XXX` will occur when `pg_lock_tracer` is started.
The software is tested with PostgreSQL versions 12, 13, 14 and 15. In order to be able to attach the _uprobes_ to the functions, they should not to be optimized away (e.g., inlined) during the compilation of PostgreSQL. Otherwise errors like `Unable to locate function XXX` will occur when `pg_lock_tracer` is started.

It is recommended to compile PostgreSQL with following CFLAGS: `CFLAGS="-ggdb -Og -g3 -fno-omit-frame-pointer"`.

Expand Down