Skip to content

Conversation

@ponychicken
Copy link
Contributor

Postgres 12 has had the final release in 2024.
Fixes #50

Postgres 12 has had the final release in 2024
@ponychicken
Copy link
Contributor Author

hi @cheerfulstoic could you have a look at this?

@cheerfulstoic
Copy link
Owner

Hey, yes! Thank you so much! Since this is a PG 13 thing which is end-of-lifeing soon, it would be nice for people to not have to think about having to set legacy_postgres_support?. I'm going to merge this and see if I can't make it automatically just do CREATE OR REPLACE from version 14 onwards. I guess there are probably some changes between 13.3.4, but I'd rather make the check easier / more reliable by just checking the first part of the version

@cheerfulstoic cheerfulstoic merged commit 48af7b0 into cheerfulstoic:main Sep 16, 2025
1 check passed
@cheerfulstoic
Copy link
Owner

Ok, 0.14.0 has been released and it should automatically figure out if it should use DROP/CREATE or CREATE OR REPLACE

@ponychicken
Copy link
Contributor Author

amazing, thats an even better solution!

@ponychicken ponychicken deleted the legacy branch September 18, 2025 09:16
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

Successfully merging this pull request may close these issues.

Problems with DROPing triggers on databases where only SELECT and TRIGGER is granted

2 participants