From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Dan Langille <dan(at)langille(dot)org> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: could not truncate directory "pg_subtrans": apparent wraparound |
Date: | 2015-06-05 22:12:53 |
Message-ID: | CAEepm=3rJd8XcyLeY14-cMbByhLe1UjYX-iScGMozPs567oXmA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Jun 6, 2015 at 9:45 AM, Dan Langille <dan(at)langille(dot)org> wrote:
> I noticed this today on my 9.4.2 server running on FreeBSD 10.1:
>
> Jun 5 18:59:40 slocum postgres[986]: [3957-1] LOG: could not truncate directory "pg_subtrans": apparent wraparound
>
> Looking at a post from 2010, Tom Lane suggest this information was useful:
>
> [root(at)slocum:/usr/local/pgsql/data/pg_subtrans] # ls -l
> total 1
> -rw------- 1 pgsql pgsql 8192 Jun 5 19:04 0032
>
> This not not a high throughput server.
It looks like subtrantransactions may have a fencepost error similar
to multixacts, described here:
I will try to repro this.
--
Thomas Munro
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2015-06-05 22:13:53 | Re: Further issues with jsonb semantics, documentation |
Previous Message | Dan Langille | 2015-06-05 21:45:43 | could not truncate directory "pg_subtrans": apparent wraparound |