I think the conclusion is to do a more thorough testing before the upgrade
next time. Have updated our playbook for upgrades to include more thorough
testing.
On Tue, Sep 30, 2025 at 8:17 PM Adrian Klaver
wrote:
> On 9/30/25 01:23, Ashish Mukherjee wrote:
> > Thank you all for your inputs.
> >
>
Thank you all for your inputs.
Well, Percona TDE was leading to the queries being very inefficient / slow
after upgrading to pgsql 17. Explain analyze shows that query planning time
shoots up crazily. A decision was taken to go back to pgsql 12, which
worked out fine as there was no incompatibilit
On Tue, 2025-09-30 at 13:53 +0530, Ashish Mukherjee wrote:
> Now the consideration is to use some other encryption option for the
> database which will work fine on pgsql 17. Cybertec's technology is
> one route, the other is EDB. I am happy to hear experiences of folks
> here with pgsql encryption
On 10/1/25 02:33, Ashish Mukherjee wrote:
I think the conclusion is to do a more thorough testing before the
upgrade next time. Have updated our playbook for upgrades to include
more thorough testing.
/I upgraded multiple non TDE databases from v12 to v17 and they are all
fine./
Then rais
On Fri, Sep 26, 2025 at 8:16 AM 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
> no
On Tue, Sep 30, 2025 at 3:47 AM Laurenz Albe
wrote:
> On Tue, 2025-09-30 at 13:53 +0530, Ashish Mukherjee wrote:
> > Now the consideration is to use some other encryption option for the
> > database which will work fine on pgsql 17. Cybertec's technology is
> > one route, the other is EDB. I am h
Hello Ashish Mukherjee,
Did you get a chance to disable JIT related parameters after PG 17
upgrade ?
If your database size in TB , try to consider pglogical bi directional
replication. you will have 17.x version and 12.x version. if you ran in to
any issue you can always switch back to old versi
On 9/30/25 01:23, Ashish Mukherjee wrote:
Thank you all for your inputs.
Well, Percona TDE was leading to the queries being very inefficient /
slow after upgrading to pgsql 17. Explain analyze shows that query
planning time shoots up crazily. A decision was taken to go back to
How did you d
No restoring to unencrypted PG 17?
On Tue, Sep 30, 2025 at 4:23 AM Ashish Mukherjee
wrote:
> Thank you all for your inputs.
>
> Well, Percona TDE was leading to the queries being very inefficient / slow
> after upgrading to pgsql 17. Explain analyze shows that query planning time
> shoots up cra
Ashish Mukherjee writes:
> When I do dump/restore like this for a test table, I get the following
> errors during restore but the table gets restored fine.
> pg_restore: error: while PROCESSING TOC:
> error: pg_restore: error: pg_restore: from TOC entry 17168; 1259
> 58572315 TABLE pkgs s14
Adrian Klaver writes:
> On 9/26/25 05:18, Ashish Mukherjee wrote:
>> 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 w
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 in
Thank you, Laurenz.
Yes, I say binary dump/restore would be faster because of the -j option.
Well, I suppose there's no certainty of what might break without going
through the whole process.
On Fri, Sep 26, 2025 at 7:57 PM Laurenz Albe
wrote:
> On Fri, 2025-09-26 at 17:48 +0530, Ashish Mukherj
On Fri, Sep 26, 2025 at 10:27 AM Laurenz Albe
wrote:
> On Fri, 2025-09-26 at 17:48 +0530, Ashish Mukherjee wrote:
>
[snip]
> > pg_restore: error: while PROCESSING TOC:
> > error: pg_restore: error: pg_restore: from TOC entry 17168; 1259
> 58572315 TABLE pkgs s14
> > pg_restore: error: pg_re
On Fri, 2025-09-26 at 17:48 +0530, Ashish Mukherjee wrote:
> 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.
>
> The
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.
The clean way seems to be text file dump and restore but this wou
16 matches
Mail list logo
