Re: could not truncate directory "pg_subtrans": apparent wraparound

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Dan Langille <dan(at)langille(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: could not truncate directory "pg_subtrans": apparent wraparound
Date: 2015-06-08 01:05:28
Message-ID: CAEepm=3_H+e17cc7WF=_ePp_-2GoZ8A0XS6CWeS1jmPQt2S=Wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 8, 2015 at 12:29 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> Here's a repro script and a suggested patch.

Argh... I realised immediately after sending this that subtransaction
truncation doesn't even use the oldest XID computed by vacuum, it uses
GetOldestXmin (the "oldest transaction that was running when any
current transaction was started"). So here is an even simpler repro,
though the fix is the same (with different comments).

--
Thomas Munro
http://www.enterprisedb.com

Attachment Content-Type Size
checkpoint-subtrans-boundary-v2.sh application/x-sh 549 bytes
fix-bogus-subtrans-wraparound-error-v2.patch application/octet-stream 946 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2015-06-08 02:52:38 Re: Memory leak with XLogFileCopy since de768844 (WAL file with .partial)
Previous Message Thomas Munro 2015-06-08 00:29:53 Re: could not truncate directory "pg_subtrans": apparent wraparound