| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tv(at)fuzzy(dot)cz>, "tigran(dot)mkrtchyan" <tigran(dot)mkrtchyan(at)desy(dot)de>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #6300: duplicate key value violates unique constraint |
| Date: | 2011-11-24 17:01:13 |
| Message-ID: | CAEYLb_W-pTGJzVENuC04fKeC0JWFUXCMCY+Do4v8R4+QkO6g1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 24 November 2011 16:55, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>
> Excerpts from Robert Haas's message of jue nov 24 13:14:38 -0300 2011:
>
>> What I think we want to distinguish between is things that are
>> PEBKAC/GIGO, and everything else. In other words, if a particular
>> error message can be caused by typing something stupid, unexpected,
>> erroneous, or whatever into psql, it's just an error. But if no
>> input, however misguided, should ever cause that symptom, then it's, I
>> don't know what the terminology should be, say, a "severe error".
>
> +1
+1
On reflection, that's better than what I proposed.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-11-24 20:31:50 | Re: libpq in android |
| Previous Message | Alvaro Herrera | 2011-11-24 16:55:17 | Re: BUG #6300: duplicate key value violates unique constraint |