Re: Long running query causing XID limit breach

2024-05-25 Thread David HJ
anyone know how to describe from this mailing list? On Thu, May 23, 2024 at 5:16 AM sud wrote: > Hello , > It's RDS postgres version 15.4. We suddenly saw the > "MaximumUsedTransactionIDs" reach to ~1.5billion and got alerted by team > members who mentioned the database is going to be in shutdow

Re: Long running query causing XID limit breach

2024-05-25 Thread sud
On Sun, May 26, 2024 at 2:24 AM yudhi s wrote: > > > *hot_standby_feedback ON and max_standby_streaming_delay = -1:* > Ensures that long-running queries on the standby are not interrupted. The > primary waits indefinitely to avoid vacuuming rows needed by standby > queries. > But Can lead to sign

Re: Long running query causing XID limit breach

2024-05-25 Thread yudhi s
On Fri, May 24, 2024 at 10:34 AM sud wrote: > I am trying to understand these two parameters and each time it looks a > bit confusing to me. If These two parameters complement or conflict with > each other. > > Say for example, If we set hot_feedback_standby to ON (which is currently > set as def

Autovacuum endless loop in heap_page_prune()?

2024-05-25 Thread Peter
Good morning, I just found Autovacuum run for 6 hours on a 8 GB table, VACUUM query doesnt cancel, cluster doesn't stop, autovacuum worker is not killable, truss shows no activity, after kill -6 this backtrace: * thread #1, name = 'postgres', stop reason = signal SIGABRT * frame #0: 0x