From: | Chris Travers <chris(at)metatrontech(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chris Travers <chris(dot)travers(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior |
Date: | 2009-12-16 22:36:21 |
Message-ID: | 5ed37b140912161436s5ec8763dr5a153e575188873@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Dec 16, 2009 at 1:39 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Chris Travers <chris(at)metatrontech(dot)com> writes:
>> trying again. Sorry for the duplicate.
>> On Wed, Dec 16, 2009 at 1:12 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2009-12-16 22:59:23 | Re: BUG #5244: Attempting to rollback to a savepoint after receiving an error with state 55000 the process hangs |
Previous Message | Robert Haas | 2009-12-16 22:17:36 | Re: Invalid explain output for multi-plan statements |