Skip to content

Commit e065ca0

Browse files
committed
test 5.2.4 pg_partman and update package docs with changed commands
1 parent 0ec8520 commit e065ca0

File tree

3 files changed

+17
-12
lines changed

3 files changed

+17
-12
lines changed

ansible/files/postgresql_config/postgresql.conf.j2

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -688,7 +688,7 @@ default_text_search_config = 'pg_catalog.english'
688688
#local_preload_libraries = ''
689689
#session_preload_libraries = ''
690690

691-
shared_preload_libraries = 'pg_stat_statements, pgaudit, plpgsql, plpgsql_check, pg_cron, pg_net, pgsodium, timescaledb, auto_explain, pg_tle, plan_filter, supabase_vault' # (change requires restart)
691+
shared_preload_libraries = 'pg_stat_statements, pgaudit, plpgsql, plpgsql_check, pg_cron, pg_net, pgsodium, timescaledb, auto_explain, pg_tle, plan_filter, supabase_vault, pg_partman_bgw' # (change requires restart)
692692
jit_provider = 'llvmjit' # JIT library to use
693693

694694
# - Other Defaults -

nix/docs/adding-new-package.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ A few things about `buildPgrxExtension_x`:
153153
2. You may need to add tests to our test.yml gh action workflow as well.
154154
3. You can add the package and name and version to `ansible/vars.yml` it is not necessary to add the sha256 hash here, as the package is already built and cached in our release process before these vars are ever run.
155155
4. to check that all your files will land in the overall build correctly, you can run `nix profile install .#psql_15/bin` on your machine, and check in `~/.nix-profile/bin, ~/.nix-profile/lib, ~/.nix-profile/share/postgresql/*` and you should see your lib, .control and sql files there.
156-
5. You can also run `nix run .#start-server 15` and in a new terminal window run `nix run .#star-client-and-migrate 15` and try to `CREATE EXTENSION <yourname>` and work with it there
156+
5. You can also run `nix run .#start-server 15` and in a new terminal window run `nix run .#start-client -- --version15` and try to `CREATE EXTENSION <yourname>` and work with it there
157157
6. Check that your extension works with the `pg_upgrade` process (TODO documentation forthcoming)
158158
7. Now you are ready to PR the extension
159159
8. From here, the release process should typically take care of the rest.

nix/ext/pg_partman.nix

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
1-
{ lib, stdenv, fetchFromGitHub, postgresql }:
1+
{
2+
lib,
3+
stdenv,
4+
fetchFromGitHub,
5+
postgresql,
6+
}:
27

38
stdenv.mkDerivation rec {
49
pname = "pg_partman";
@@ -7,10 +12,10 @@ stdenv.mkDerivation rec {
712
buildInputs = [ postgresql ];
813

914
src = fetchFromGitHub {
10-
owner = "pgpartman";
11-
repo = pname;
12-
rev = "refs/tags/v${version}";
13-
sha256 = "sha256-i/o+JZEXnJRO17kfdTw87aca28+I8pvuFZsPMA/kf+w=";
15+
owner = "pgpartman";
16+
repo = "${pname}";
17+
rev = "refs/tags/v${version}";
18+
hash = "sha256-i/o+JZEXnJRO17kfdTw87aca28+I8pvuFZsPMA/kf+w=";
1419
};
1520

1621
installPhase = ''
@@ -24,10 +29,10 @@ stdenv.mkDerivation rec {
2429

2530
meta = with lib; {
2631
description = "Partition management extension for PostgreSQL";
27-
homepage = "https://github.com/pgpartman/pg_partman";
28-
changelog = "https://github.com/pgpartman/pg_partman/blob/v${version}/CHANGELOG.md";
29-
platforms = postgresql.meta.platforms;
30-
license = licenses.postgresql;
31-
broken = versionOlder postgresql.version "14";
32+
homepage = "https://github.com/pgpartman/pg_partman";
33+
changelog = "https://github.com/pgpartman/pg_partman/blob/v${version}/CHANGELOG.md";
34+
platforms = postgresql.meta.platforms;
35+
license = licenses.postgresql;
36+
broken = versionOlder postgresql.version "14";
3237
};
3338
}

0 commit comments

Comments
 (0)