Repository navigation
Postgres 15 support - #729
Conversation
97053ed to
4315d27
Compare
|
acd72dc to
4840ad2
Compare
|
PostgreSQL 15 is released! 🎉 I updated the PR so that it runs PostgreSQL 15 in CI now that APT packages are available. I've also removed the code that used the release candidate version so that it always uses the actual release now. |
amazing! Thanks a billion. We'll get this merged next week. I think we're kinda already heading towards a 0.5.1, so this will be awesome to get included. Also, it's probably close enough for us to go ahead and remove v10 support. I'm planning on volunteering @BradyBonnette for that. |
ebffdb7 to
346f90c
Compare
Alternatively, doing nothing here would push folks not to glob import pg_sys, which is kind of a good thing... I suppose that kind of change might be better done over a major bump, though. |
The amount of breakage from adding |
|
That extension will require more updates to build in any case, unfortunately, since we changed a fair number of API details it relies on. |
|
Any update on when we might be able to get this PR in? |
|
this looks pretty good. I hacked @zombodb to use this and after a few tweaks for |
|
Thanks @Smittyvb! We appreciate the contribution. |
…led to include the pg15 bindings
Adds support for PostgreSQL 15.
Main changes:
pg15feature to indicate compatibility with PostgreSQL 15.cargo pgx newautomatically adds the feature for new extensions.pg_sys::Stringnow exists, which conflicts with the stdStringwhen importingpg_sys::*abi_extrafield in thePg_magic_functhat is always"PostgreSQL", but might be different on PostgreSQL forks with an incompatible ABIpg_sys::Valuedoesn't exist anymore