| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Snapshot too old logging |
| Date: | 2016-11-15 16:29:52 |
| Message-ID: | 26790.1479227392@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kevin Grittner <kgrittn(at)gmail(dot)com> writes:
> On Tue, Nov 15, 2016 at 3:38 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Is there a reason why we don't log which relation triggered the snapshot too
>> old error when it happens?
> I would probably not want to mess with the text of the error
> itself, in case any client-side software bases recovery on that
> rather than the SQLSTATE value;
Any such code is broken on its face because of localization.
Perhaps including the relname in the main message would make it
unduly long, but if not I'd vote for doing it that way.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-11-15 16:30:33 | Re: Something is broken about connection startup |
| Previous Message | Robert Haas | 2016-11-15 16:27:14 | Re: pg_dump, pg_dumpall and data durability |