From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ashish Mukherjee <ashish(dot)mukherjee(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Downgrade pgsql 17 to pgsql 12 question |
Date: | 2025-09-26 15:10:03 |
Message-ID: | d061e898-9a81-411b-9ecf-fb928321caff@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/26/25 05:18, Ashish Mukherjee 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.
>
What are the incompatibilities?
Might be easier to deal with those then doing the below.
> The clean way seems to be text file dump and restore but this would be
> too huge and too slow for our database of 3T. If I use pg_dump v17 and
> then restore with pg_restore v 17 on a pgsql v12 database, is there any
> risk? I tried a small test with a bunch of tables and it worked, but am
> wondering about the pitfalls. I am restoring from the directory format dump.
>
> When I do dump/restore like this for a test table, I get the following
> errors during restore but the table gets restored fine.
> Any input would be appreciated.
>
> Regards,
> Ashish
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-09-26 15:13:57 | Re: Downgrade pgsql 17 to pgsql 12 question |
Previous Message | Ashish Mukherjee | 2025-09-26 14:47:12 | Re: Downgrade pgsql 17 to pgsql 12 question |