Re: 8.3.0 backend segfaults - Mailing list pgsql-bugs

From Greg Sabino Mullane
Subject Re: 8.3.0 backend segfaults
Date
Msg-id a6bc74769b68021042e413a857b012d0@biglumber.com
Whole thread Raw
In response to 8.3.0 backend segfaults  ("Alex Hunsaker" <badalex@gmail.com>)
Responses Re: 8.3.0 backend segfaults
Re: 8.3.0 backend segfaults
List pgsql-bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> Work load is a web application where each page beings a transaction;
> creates a temp table, does a few selects, inserts and updates and the
> commits.

Are you sure you are calling DBI->connect *after* the Apache children
are created? Major problems like this can happen if not. The use of
prepare_cached() may be adding to the problem as well, especially if
you are using temp tables. In DBD::Pg, prepared statements are not
actually prepared (in most cases) until just before the first execute,
to account for late bindings and to be more efficient. Some related
DBD::Pg attribs to look at are pg_server_prepare and pg_prepare_now.


- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200803121121
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkfX9Q0ACgkQvJuQZxSWSsjEjACg6QNUdPIw5gczfTtFK3aUMh39
fUYAoLwRrFZ75z2Fbq7GDRYqgTlRsR9N
=ngbh
-----END PGP SIGNATURE-----

pgsql-bugs by date:

Previous
From: Laurent Birtz
Date:
Subject: Re: LISTEN/NOTIFY race condition?
Next
From: Tom Lane
Date:
Subject: Re: 8.3.0 backend segfaults