Re: SSI bug?
YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
From: yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi)
To: Kevin.Grittner@wicourts.gov
Cc: drkp@csail.mit.edu, heikki.linnakangas@enterprisedb.com, pgsql-hackers@postgresql.org
Date: 2011-04-08T03:36:29Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Update key words table for 9.1
- bf6848bc8c82 9.1.0 cited
-
Documented some ecpg command line options that were missing:
- 71ac48fd9ceb 9.1.0 cited
hi, > YAMAMOTO Takashi <yamt@mwd.biglobe.ne.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