Re: Polecat "quit unexpectdly"

Kevin Grittner <kevin.grittner@wicourts.gov>

From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>

To: "Robert Creager" <Robert.Creager@Oracle.com>

Cc: <pgbuildfarm-members@pgfoundry.org>,<pgsql-hackers@postgresql.org>

Date: 2011-06-14T20:39:00Z

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 →

Oops, forgot to change the order of entries in 2PC callback arrays when I
- 85ea93384ae2 9.2.0 cited
Renumber 2PC resource managers so that compared to 9.0, predicate lock rmgr
- b81831acbc67 9.2.0 cited

Robert Creager <Robert.Creager@Oracle.com> wrote:

> You believe it was related to the flurry of errors that popped up
> then.

I haven't looked at all the error in the "flurry".  I think your
particular report is consistent with being caused by this commit:

http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=b81831acbc671445061ed41a55fb1cc21d8e2979

and solved by this one:

http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=85ea93384ae21ff59f5e5b292884a86f9c10b852

I suspect that other builds based on checkouts in this window of
time would probably show similar errors.

-Kevin