Re: Reaping Temp tables to avoid XID wraparound

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: James Sewell <james(dot)sewell(at)jirotech(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reaping Temp tables to avoid XID wraparound
Date: 2019-02-19 03:36:48
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Feb 19, 2019 at 10:52:54AM +1100, James Sewell wrote:
> I agree the use case is narrow - but it's also pretty critical.


> I suppose an in-core way of disconnecting idle sessions after x time would
> work too - but that seems like a sledgehammer approach.

Such solutions at SQL level need to connect to a specific database and
I implemented one for fun, please see the call to
BackgroundWorkerInitializeConnection() here:

So that's not the end of it as long as we don't have a cross-database
solution. If we can get something in PGPROC then just connecting to
shared memory would be enough.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Higuchi, Daisuke 2019-02-19 04:04:10 [Bug Fix] ECPG: could not use set xxx to default statement
Previous Message Michael Paquier 2019-02-19 03:26:40 Re: Prepared transaction releasing locks before deregistering its GID