| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Snapshot too old logging |
| Date: | 2016-11-15 09:38:27 |
| Message-ID: | CABUevEzYCH5JJaqGrN3Vgwt84DZDC02q5vid7XsauEHf87aPSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Is there a reason why we don't log which relation triggered the snapshot
too old error when it happens?
Since we do have Relation available in TestForOldSnapshot_impl(), shouldn't
we be able to include it?
Having that in the log message would be very helpful, but is there a reason
why it wouldn't work?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2016-11-15 09:51:42 | Re: Declarative partitioning - another take |
| Previous Message | Aleksander Alekseev | 2016-11-15 08:03:24 | Re: [PATCH] Generic type subscription |