Re: Remembering bug #6123 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Remembering bug #6123
Date
Msg-id 22192.1326500263@sss.pgh.pa.us
Whole thread Raw
In response to Re: Remembering bug #6123  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> However, I wonder what use-case led you to file bug #6123 to begin
>> with.

> [ details ]
> Hopefully this answers your question.  I went looking for details on
> particular failures here, but didn't have luck with so far.  I can
> try again if more detail like that would help.

Well, the bottom line that's concerning me here is whether throwing
errors is going to push anyone's application into an unfixable corner.
I'm somewhat encouraged that your Circuit Courts software can adapt
to it, since that's certainly one of the larger and more complex
applications out there.  Or at least I would be if you had actually
verified that the CC code was okay with the recently-proposed patch
versions.  Do you have any thorough tests you can run against whatever
we end up with?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: [COMMITTERS] pgsql: Fix breakage from earlier plperl fix.
Next
From: Andres Freund
Date:
Subject: Re: Command Triggers