Skip site navigation (1) Skip section navigation (2)

DBD::Pg returns "DBD::Pg::st execute failed: connection not open"

From: "Thomas Adam" <thomas(dot)adam22(at)gmail(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: DBD::Pg returns "DBD::Pg::st execute failed: connection not open"
Date: 2008-01-30 15:56:48
Message-ID: 18071eea0801300756m7d1d2273n16ffb2323f2998a3@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
Hello all,

I'm having an odd issue and was wondering if someone could point me in
the right direction.  I hope this is also on the correct list.  If
not, let me know.

I'm using Perl 5.8.8 with DBD-Pg-1.49.  I have a perl script which
periodically inserts information into a database.  All of this has
been working fine for ages.  But very recently, and for some unknown
reason, my script stops working, the error being:

DBD::Pg::st execute failed: connection not open

I had previously set DBI->trace(4) and found out that my script was
able to connect just fine to the database, and perform SELECT queries,
but as soon as it came to running an INSERT query, the script
segfaults [1].

Now, at this point, I am confused.  I know, because I have tested it
on another machine, that the data in question works just fine.
Neither, does this issue seem to revolve around the data, as far as I
can work out, this "error" is completely intermittent.  But as soon as
it happens, it's fatal.  Even after I clean out the postgres database
(i.e., delete all the files pertaining to that database) and rebuild
it, the error still remains.

This does suggest to me that there's some weird interaction between
the DBD-Pg libraries and the underlying C code?  Has anyone got any
idea what might be going on?  The closest piece of information I have
is in this post:

http://archives.postgresql.org/pgsql-general/2000-02/msg00205.php

Although unlike him, I am actually able to perform SELECT/INSERT
queries via psql after this "connection not open" error just fine ---
which does suggest to me more that something is amiss with the DBD-Pg
<-> C interaction somewhere.

Can anyone shed any light on this?   If you need further information,
don't hesitate to ask, and I'll see what I can do.

Kindly,

Thomas Adam

[1]  Well, the *perl* does, at any rate.  Whether or not it's the
postgres daemon which kicks it out, or the client itself is unclear.
I'm going to guess the client, since the daemon still runs.

Responses

pgsql-interfaces by date

Next:From: Greg Sabino MullaneDate: 2008-02-05 05:25:58
Subject: Re: DBD::Pg returns "DBD::Pg::st execute failed: connection not open"
Previous:From: Markus SchiltknechtDate: 2008-01-29 09:46:46
Subject: Re: Is there an interface that...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group