| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Problem with error response message |
| Date: | 2012-05-22 17:55:41 |
| Message-ID: | CA+U5nMJdWPc=mOULf7Wf7GJfAfiPdN7FB8BC1ZU7kJiM+tq8Bg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22 May 2012 12:59, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
> Also I wonder why "conflict with recovery" generates same error code
> as serialization error. For me it seems not very consistent
> choice. IMO, we should assign different error code for at least brings
> totally different effect to frontend: aborting transactions or
> sessions.
Some conflicts cause ERROR, some cause FATAL. So there is not a
distinct difference.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2012-05-22 17:56:17 | Re: Changing the concept of a DATABASE |
| Previous Message | Daniel Farina | 2012-05-22 17:51:40 | Re: Changing the concept of a DATABASE |