From: | Jan Wieck <jan(at)wi3ck(dot)info> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_upgrade does not upgrade pg_stat_statements properly |
Date: | 2021-07-15 18:14:28 |
Message-ID: | 042edcd3-f466-047b-3de5-c816d55417e9@wi3ck.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7/15/21 1:10 PM, David G. Johnston wrote:
> ... But while
> PostgreSQL doesn't really have a choice here - it cannot be expected to
> subdivide itself - extensions (at least external ones - PostGIS is one I
> have in mind presently) - can and often do attempt to support multiple
> versions of PostgreSQL for whatever major versions of their product they
> are offering. For these it is possible to adhere to the "change one
> thing at a time principle" and to treat the extensions as not being part
> of "ALL the changes from one major version to the target version..."
You may make that exception for an external extension like PostGIS. But
I don't think it is valid for one distributed in sync with the core
system in the contrib package, like pg_stat_statements. Which happens to
be the one named in the subject line of this entire discussion.
Regards, Jan
--
Jan Wieck
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2021-07-15 18:26:24 | Re: pg_upgrade does not upgrade pg_stat_statements properly |
Previous Message | John Naylor | 2021-07-15 18:12:43 | Re: speed up verifying UTF-8 |