From: | James Sewell <james(dot)sewell(at)jirotech(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Reaping Temp tables to avoid XID wraparound |
Date: | 2019-02-13 00:04:51 |
Message-ID: | CAANVwEveL6k+n7p+f_tY8s=Vnc6Acpjn1NyOxMPOCJAZXFrF6w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all,
I hit an issue yesterday where I was quickly nearing XID wraparound on a
database due to a temp table being created in a session which was then left
IDLE out of transaction for 6 days.
I solved the issue by tracing the owner of the temp table back to a session
and terminating it - in my case I was just lucky that there was one session
for that user.
I'm looking for a way to identify the PID of the backend which owns a temp
table identified as being an issue so I can terminate it.
From the temp table namespace I can get the backend ID using a regex - but
I have no idea how I can map that to a PID - any thoughts?
Cheers,
James Sewell,
Suite 112, Jones Bay Wharf, 26-32 Pirrama Road, Pyrmont NSW 2009
*P *(+61) 2 8099 9000 <(+61)%202%208099%209000> *W* www.jirotech.com *F *
(+61) 2 8099 9099 <(+61)%202%208099%209000>
--
The contents of this email are confidential and may be subject to legal or
professional privilege and copyright. No representation is made that this
email is free of viruses or other defects. If you have received this
communication in error, you may not copy or distribute any part of it or
otherwise disclose its contents to anyone. Please advise the sender of your
incorrect receipt of this correspondence.
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2019-02-13 00:23:35 | RE: Protect syscache from bloating with negative cache entries |
Previous Message | Jeff Janes | 2019-02-12 22:38:28 | Re: Bloom index cost model seems to be wrong |