| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Maciej Jaros <egil(at)wp(dot)pl> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19927: PostgreSQL 16: SQL dump adds experimental/incompatible options like \restrict |
| Date: | 2026-11-21 00:16:37 |
| Message-ID: | 330C87A3-2475-4FF7-9711-B207E1FA8368@thebuild.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On Nov 20, 2026, at 15:31, Maciej Jaros <egil(at)wp(dot)pl> wrote:
> If minor versions can introduce breaking changes that aren't immediately obvious, I also need to test the specific PostgreSQL version before deploying it.
You are over-generalizing here. There is one particular contract that you expected to exist that doesn't, which is that a pg_dump taken from a later version can be restored to an earlier version with no errors. (Note that in this particular case, the restore actually does work, you just get an alarming-looking error message.) Taking that one change to mean all bets are off and every new minor version of PostgreSQL can introduce arbitrary changes that might break anything isn't supported by the real history of the project.
And it's good practice to test even minor releases of PostgreSQL before deploying them in production, because even "non-breaking" changes can result in things like different query plans that can affect system performance. It's most definitely never been the case that the project has guaranteed that new minor versions will have no observable differences in behavior from prior versions.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2026-11-21 01:15:52 | Re: BUG #19924: unrecognized node type in create_plan_recurse: UNION, LIMIT, json_populate_recordset, inheritance |
| Previous Message | surya poondla | 2026-11-20 23:47:16 | Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY |