On Wed, Dec 16, 2009 at 1:39 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Chris Travers <ch...@metatrontech.com> writes: >> trying again. Sorry for the duplicate. >> On Wed, Dec 16, 2009 at 1:12 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: >>> Exactly what "frontend" are you talking about here? Because what this >>> sounds like to me is a client-side programming error. It's certainly >>> not the backend's fault, and I doubt it is libpq's either. > >> I am using DBD::Pg. > >> I asked about it on #postgresql and was told this was the SQLSTATE code >> passed up from libpq (by the author of DBD::Pg). Several other folks >> there seemed to concur. > > Could you provide a self-contained test case? And what versions of > DBD::Pg etc are we talking about?
Just to weed out possibilities of DBD::Pg behavior causing this, I am going to try to create a straight C test case. If I can't I will end the perl scripts I was using to test. Best Wishes, Chris Travers > > regards, tom lane > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
