I am trying to use pg_hint_tables in AWS Aurora Postgres. I changed the
Postgres parameter "pg_hint_plan.enable_hint_table = 1". Then I logout but
can't login anymore with the following error message.
“postgres@postgres:[2719]:ERROR: relation "hint_plan.hints" does not exist at
character 21”
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
On Tue, Sep 16, 2025 at 12:44 PM Adrian Klaver
wrote:
>
> On 9/16/25 04:01, Jaime Casanova wrote:
> > Hi,
> >
> > I have a database with UTF8 encoding. This database seems to be
> > receiving data in WIN1252 encoding from some client.
> >
[...]
> >
> > Some time ago I tried to create a logical rep
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
On Fri, 26 Sep 2025, Laurenz Albe wrote:
On Fri, 2025-09-26 at 12:05 +, Dan Mahoney (Gushi) wrote:
In the interest of automation, I've set up a pgpass file for my
pg_basebackup between master and standby. This all works, thusly:
pg_basebackup -d
'postgres://[email protected]:5432/foo?sslmo
Hi! I have an idea.
I think there's some historical confusion near to FOR UPDATE in a SELECT
statement, because this should be called FOR KEY UPDATE or something like.
It's currently impossible to rename it, but it's possible to introduce
optional keyword KEY:
FOR [KEY] UPDATE
Those pedants who
