| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, simon(at)2ndquadrant(dot)com, fgp(at)phlo(dot)org, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Error code for "terminating connection due to conflict with recovery" |
| Date: | 2011-01-31 16:24:22 |
| Message-ID: | AANLkTik5jiSeSaa=0CYHW8HAATsGrcer9+wHHyYc749Z@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 31, 2011 at 10:31 AM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> As a novice I am not sure why we _wouldn't_ create two new
>> separate error codes
>
> The argument for using SQLSTATE 40001 for failures which are
> strictly due to concurrency problems, and are likely to work if the
> transaction is retried, is that there is already a lot of software
> which knows how to do that. On the other hand, going into such code
> to turn that into a list of concurrency failure states is probably
> only going to cause pain to those with applications intended to work
> with multiple DBMS products without much modification.
Yeah, I think that one's pretty logical. I think my vote is to either
change the drop-database case to be the same as that, or to use a new
error code. ERRCODE_ADMIN_SHUTDOWN is just strange.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-01-31 16:25:38 | Re: Add ENCODING option to COPY |
| Previous Message | Bruce Momjian | 2011-01-31 15:51:09 | Re: Error code for "terminating connection due to conflict with recovery" |