| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Snapshot too old logging |
| Date: | 2016-11-16 13:39:11 |
| Message-ID: | CACjxUsMRuH8QJxx-ozJVSC24qj40_6Q_8YX+U7Dfce2idLfQHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 16, 2016 at 6:12 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Tue, Nov 15, 2016 at 9:23 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>> Can this happen for relation types other than tables, say materialized
>> views? (Your suggested wording omits relation type so it wouldn't be
>> affected, but it's worth considering I think.)
>
>
> I'm fairly certain it can hit other things, including indexes and definitely
> matviews, but I won't say I'm 100% sure :) The check is at block level. Does
> errtable() work for that? (I've never used it, and it seems it's only
> actually use din a single place in the codebase..)
Yes, it can happen for indexes and for materialized views.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2016-11-16 13:40:21 | Re: Parallel execution and prepared statements |
| Previous Message | Robert Haas | 2016-11-16 12:46:24 | Re: Password identifiers, protocol aging and SCRAM protocol |