Re: SSI bug?

From: yamt(at)mwd(dot)biglobe(dot)ne(dot)jp (YAMAMOTO Takashi)
To: Kevin(dot)Grittner(at)wicourts(dot)gov
Cc: drkp(at)csail(dot)mit(dot)edu, heikki(dot)linnakangas(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: SSI bug?
Date: 2011-04-08 03:36:29
Message-ID: 20110408033629.F14CD19CF07@mail.netbsd.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

hi,

> YAMAMOTO Takashi <yamt(at)mwd(dot)biglobe(dot)ne(dot)jp> wrote:
>
>> LOG: could not truncate directory "pg_serial": apparent
>> wraparound
>
> Did you get a warning with this text?:
>
> memory for serializable conflict tracking is nearly exhausted

there is not such a warning near the above "aparent wraparound" record.
not sure if it was far before the record as i've lost the older log files.

YAMAMOTO Takashi

>
> If not, there's some sort of cleanup bug to fix in the predicate
> locking's use of SLRU. It may be benign, but we won't really know
> until we find it. I'm investigating.
>
> -Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-04-08 03:40:11 Re: GSoC 2011 Eager MV implementation proposal
Previous Message Robert Haas 2011-04-08 03:30:50 Re: WIP: Allow SQL-language functions to reference parameters by parameter name