Re: [GENERAL] Pg + perl + apache

2004-02-18 Thread Lincoln Yeoh
You could try something like this: Assuming you are using perl+DBI (as per your examples). If you are using modperl: [modperl can override the "connect to db" for connection reuse/pooling] begin cgi web app: connect to db rollback do stuff do more stuff commit if ok by default rollback disconnect

Re: [GENERAL] Pg + perl + apache

2004-02-15 Thread Ian Barwick
On Saturday 14 February 2004 22:35, Michael L. Artz wrote: (...) > If anyone has seen anything like this before (i.e. random errors in a > similar apache/mod_perl) situation, or might have any pointers as to > where to look next, let me know. What would cause postgres to return an > error for a se

Re: [GENERAL] Pg + perl + apache

2004-02-15 Thread Tom Lane
"Michael L. Artz" <[EMAIL PROTECTED]> writes: > Anway, DBD::Pg throws random errors into my logs, along the lines of > what is below (the lines beginning with SQL are debug statements from > the script, and are the lines references by the DBD error. > LOG: statement: SELECT session

Re: [GENERAL] Pg + perl + apache

2004-02-15 Thread Martijn van Oosterhout
On Sat, Feb 14, 2004 at 04:35:58PM -0500, Michael L. Artz wrote: > I'm having some odd issues, but I'm not sure exactly the cause of them, > but postgres is the component in the system that is throwing the errors, > so I thought I'd start here. > with the corresponding postgresql.log entry bein