| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Brad DeJong <Brad(dot)Dejong(at)infor(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Snapshot too old logging |
| Date: | 2016-11-18 17:24:30 |
| Message-ID: | CA+Tgmob=mL2aHgYpBWJtOi_jLyXdLt8PQrhb1Mm_L7rOTvu3Kg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 18, 2016 at 11:49 AM, Brad DeJong <Brad(dot)Dejong(at)infor(dot)com> wrote:
> On Wed, Nov 16, 2016 at 6:43 AM, Robert Haas wrote:
>> I think I was suggesting: One or more rows required by this query may
>> already have been removed from "%s".
>
> I keep reading that as "you have data corruption because something removed rows that your query needs" rather than "this query took too long to complete but may succeed if you resubmit it".
I see your point, but remember that this would only the detail line.
The error would still be "snapshot too old".
ERROR: snapshot too old
DETAIL: One or more rows required by this query may already have been
removed from "%s".
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-11-18 17:29:19 | Re: Patch: Implement failover on libpq connect level. |
| Previous Message | Robert Haas | 2016-11-18 17:23:01 | Re: Declarative partitioning - another take |