May be I am wrong here, but is it not the classic case of connections open
too long idle in TX and xid wraparound ?
How is connection pool (and which one ?)
adding to the woes?
I mean the same can be a problem with direct connections too right ?
We use pgbouncer with mostly TX level pooling which
In conjunction with some parameter to renew idle connections and those that
have been opened for too long will help you prevent this in the future,
this also helps prevent server processes from becoming too big memory wise.
On Wed, Mar 13, 2019 at 4:32 PM Rene Romero Benavides <
rene.romer...@gma
Wow, thanks for sharing your experience. What kind of connection pooling
are we talking about? some connection pools implement a DISCARD ALL
statement after a session close, that may help if possible to configure.
On Wed, Mar 13, 2019 at 4:21 AM Jahwan Kim wrote:
> Hi all,
>
>
> I'd like to shar
Hi all,
I'd like to share my (painful) experience, in which temp tables caused
PostgreSQL shutdown.
TL;DR. Do not use temp tables in PostgreSQL with connection pool.
* My app uses connection pool AND temp tables, with default setting of ON
COMMIT PRESERVE ROWS.
* I found out later that autovacuu
