| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "George Pavlov" <gpavlov(at)mynewplace(dot)com> |
| Cc: | "PostgreSQL general" <pgsql-general(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: apparent wraparound |
| Date: | 2006-11-11 01:21:41 |
| Message-ID: | 8274.1163208101@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"George Pavlov" <gpavlov(at)mynewplace(dot)com> writes:
>> "George Pavlov" <gpavlov(at)mynewplace(dot)com> writes:
>>>>> 2006-11-08 12:38:34 PST [3739]: [3-1] LOG: could not truncate directory
>>>>> "pg_multixact/members": apparent wraparound
>>>> During crash recovery?
>>> no crashes, just normal DB operation...
>>
>> Hmm ... what is in pg_multixact/members/ again?
> Now there is only a file named 0010 the date on which changes about
> every 4-5 minutes or so.
AFAICS this must indicate that TruncateMultiXact() computed a bogus
oldestOffset, but it's hard to see how that would happen in the middle
of an unexceptional run. Alvaro, any ideas? Could there be a race
condition involved in filling in the "members" entries?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shane Ambler | 2006-11-11 02:35:54 | Re: Request for replication advice |
| Previous Message | George Pavlov | 2006-11-11 00:50:38 | Re: apparent wraparound |