Re: Problem with a Query

Siraj G writes: > We migrated a PgSQL database from Cloud SQL to compute engine and since > then there is a SQL we observed taking a long time. After some study, I > found that the SQL is using NESTED LOOP where the cost is too high. The core of your problem seems to be here: >

Problem with a Query

Hello! We migrated a PgSQL database from Cloud SQL to compute engine and since then there is a SQL we observed taking a long time. After some study, I found that the SQL is using NESTED LOOP where the cost is too high. I tried VACUUM FULL and ANALYZE, but to no avail. Only when I disabled the nest

Re: 回复：searching for libpq5-14.1-42PGDG.rhel8.x86_64

Hi, On Mon, 2024-08-12 at 12:54 +0800, 王瞿 wrote: > It returned “Access Denied” when I access the archive repo. > Did I miss sonething？ As I responded you on our issue tracker, old packages for libpq5 is not available. I also provided you solutions: https://redmine.postgresql.org/issues/8025#note

Re: autovacuum freeze recommendations at table level

Hi Durga *autovacuum_freeze_max_age* specifies the maximum age (in transactions) that a table's tuples can reach before a vacuum is forced to prevent transaction ID wraparound. when the age of the oldest tuple in the table exceeds this value, an autovacuum is triggered to freeze the tuples. *Recom