| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <kgrittn(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Snapshot too old logging |
| Date: | 2016-11-15 18:30:10 |
| Message-ID: | CABUevEzMkb3TzD91RCCdn0o8_DUmusJ-RSeN+3p9Xjm6A4P29A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 15, 2016 at 7:27 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Nov 15, 2016 at 1:18 PM, Magnus Hagander <magnus(at)hagander(dot)net>
> wrote:
> > Is there value in showing which snapshot as well? Something like:
> > DETAIL: snapshot <xyz> is too old to access relation <relation>
>
> IIUC, the granularity is per-block, not per-relation, so that might be
> misleading.
>
Does it help to let the user know which number? I'm not really sure what
I'd do with that information, whereas knowing the relation would be very
useful.
But we could certainly say "snapshot <xyz> is too old to access block <nnn>
of relation <rel>".
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brad DeJong | 2016-11-15 18:33:55 | Re: Snapshot too old logging |
| Previous Message | Robert Haas | 2016-11-15 18:28:47 | Re: Patch: Implement failover on libpq connect level. |