Re: thread safety on clients - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: thread safety on clients
Date
Msg-id 200912110055.nBB0tFE29298@momjian.us
Whole thread Raw
In response to Re: thread safety on clients  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: thread safety on clients  (Greg Smith <greg@2ndquadrant.com>)
List pgsql-hackers
Peter Eisentraut wrote:
> > starting vacuum...end.
> > TRAP: FailedAssertion("!((data - start) == data_size)", File:
> > "heaptuple.c", Line: 255)
> > Client 0 aborted in state 8. Probably the backend died while processing.
> > LOG:  server process (PID 30713) was terminated by signal 6: Aborted
> > TRAP: FailedAssertion("!((data - start) == data_size)", File:
> > "heaptuple.c", Line: 255)
> > Client 8 aborted in state 8. Probably the backend died while processing.
> > LOG:  terminating any other active server processes
> > WARNING:  terminating connection because of crash of another server process
> > DETAIL:  The postmaster has commanded this server process to roll back
> > the current transaction and exit, because another server process
> > exited abnormally and possibly corrupted shared memory.
> > """
> > 
> > if i remove the -j option then it runs without a problem
> 
> Possibly related to the incomplete removal of the enable-thread-safety
> option that I just posted about.

I thought about that but I can't figure out how that would affect
pgbench.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] Installing PL/pgSQL by default
Next
From: Alvaro Herrera
Date:
Subject: Re: Viewing table data only from its corresponding oid-named file