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

PG17 compatibility #404

Open
Deltaus opened this issue Jun 4, 2024 · 2 comments
Open

PG17 compatibility #404

Deltaus opened this issue Jun 4, 2024 · 2 comments

Comments

@Deltaus
Copy link

Deltaus commented Jun 4, 2024

Hi there, Postgres 17beta1 has been released by community and the latest released tag 1.5.0 doesn't build with it. However, the unpublished v1.5.1 does work with PG17, so may I know when v1.5.1 will be officially released? Thanks

@andreasscherbaum
Copy link
Collaborator

@Deltaus Can you please check if that is working for you now?

@df7cb
Copy link
Contributor

df7cb commented Sep 13, 2024

@andreasscherbaum 1.5.1 has not been tagged yet.

1.5.0 fails with this regression diff:

diff -U3 /home/myon/projects/postgresql/pg-repack/pg-repack/regress/expected/repack-check.out /home/myon/projects/postgresql/pg-repack/pg-repack/regress/results/repack-check.out
--- /home/myon/projects/postgresql/pg-repack/pg-repack/regress/expected/repack-check.out	2023-11-22 21:10:39.000000000 +0100
+++ /home/myon/projects/postgresql/pg-repack/pg-repack/regress/results/repack-check.out	2024-09-13 22:53:25.018310529 +0200
@@ -128,7 +128,7 @@
  attname | attstattarget |    attoptions     
 ---------+---------------+-------------------
  i       |             1 | 
- t       |            -1 | {n_distinct=-0.5}
+ t       |               | {n_distinct=-0.5}
 (2 rows)
 
 --

I can't easily tell if this is harmless. Could a new release with PG17 support be tagged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants