| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Ashish Mukherjee <ashish(dot)mukherjee(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Downgrade pgsql 17 to pgsql 12 question |
| Date: | 2025-09-28 23:40:44 |
| Message-ID: | CAHyXU0ynqbCHrw3XvofEzidHow4tx1FFGNB2FUR5-wj-EhLcNQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Sep 26, 2025 at 8:16 AM Ashish Mukherjee <ashish(dot)mukherjee(at)gmail(dot)com>
wrote:
> Hello,
>
> I have a strange requirement to downgrade from pgsql 17 to pgsql 12. This
> is because we found in production certain incompatibilities between both
> versions for our database. It should have been caught in testing but was
> not.
>
Agree with others that snap downgrade is not necessarily a good choice
here. Either way, if I were in your shoes, I'd be loading a plain text
dump, maybe with some light massaging to strip out some compatibility
issues.
Can you let us know what the hang up is? Version upgrades these days are
usually pretty painless except for some performance issues, unless you have
some unusual situations, for example, exotic extensions.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Idiong | 2025-09-29 06:22:36 | No POSTGIS in PostgreSQL 18 |
| Previous Message | Adrian Klaver | 2025-09-28 21:17:30 | Re: PostgreSQL 18 not available for Noble? |