Horton

Re: [Pgbuildfarm-members] Polecat "quit unexpectdly"

Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>

View thread
From: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
To: pgbuildfarm-members@pgfoundry.org
Date: 2011-06-14T16:58:40Z
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 →

  1. Oops, forgot to change the order of entries in 2PC callback arrays when I

  2. Renumber 2PC resource managers so that compared to 9.0, predicate lock rmgr

On 06/14/2011 06:45 PM, Robert Creager wrote:
> 
> Stack trace, nothing else.  Now that the horse has left the barn, I changed to keep error builds...
> 
> Process:         postgres [17457]
> Path:            /Volumes/High Usage/usr/local/src/build-farm-4.4/builds/HEAD/pgsql.6849/src/test/regress/tmp_check/install/usr/local/src/build-farm-4.4/builds/HEAD/inst/bin/postgres
> Identifier:      postgres
> Version:         ??? (???)
> Code Type:       X86-64 (Native)
> Parent Process:  postgres [17136]
> 
> Date/Time:       2011-06-14 05:00:27.466 -0600
> OS Version:      Mac OS X 10.6.7 (10J869)
> Report Version:  6
> 
> Interval Since Last Report:          658000 sec
> Crashes Since Last Report:           1
> Per-App Crashes Since Last Report:   1
> Anonymous UUID:                      77053C10-A2B5-4078-A796-5862E233A1AC
> 
> Exception Type:  EXC_CRASH (SIGABRT)
> Exception Codes: 0x0000000000000000, 0x0000000000000000
> Crashed Thread:  0  Dispatch queue: com.apple.main-thread
> 
> Application Specific Information:
> abort() called
> 
> Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
> 0   libSystem.B.dylib             	0x00007fff821815d6 __kill + 10
> 1   libSystem.B.dylib             	0x00007fff82221cd6 abort + 83
> 2   postgres                      	0x00000001002fcd52 0x100000000 + 3132754
> 3   postgres                      	0x000000010005cafa multixact_twophase_postcommit + 74 (multixact.c:1367)
> 4   postgres                      	0x000000010005deab ProcessRecords + 91 (twophase.c:1407)
> 5   postgres                      	0x000000010005f78a FinishPreparedTransaction + 1610 (twophase.c:1368)
> 6   postgres                      	0x0000000100236a5a PortalRunUtility + 298 (palloc.h:88)
> 7   postgres                      	0x00000001002381c5 PortalRunMulti + 597 (pquery.c:1315)
> 8   postgres                      	0x0000000100238b78 PortalRun + 984 (pquery.c:817)
> 9   postgres                      	0x0000000100234b2d exec_simple_query + 589 (postgres.c:1025)
> 10  postgres                      	0x00000001002356f1 PostgresMain + 1937 (postgres.c:3926)
> 11  postgres                      	0x00000001001e82ec ServerLoop + 2780 (postmaster.c:3600)
> 12  postgres                      	0x00000001001e9251 PostmasterMain + 2753 (postmaster.c:1120)
> 13  postgres                      	0x000000010017c305 main + 965 (main.c:199)
> 14  postgres                      	0x0000000100000b14 start + 52


this looks like it was caused by:


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

but should now be fixed by:

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


Stefan