Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> writes:
> Can we have a "soft" hot standby conflict that doesn't kill the query,
> but disables index-only-scans?
Well, there wouldn't be any way for the planner to know whether an
index-only scan would be safe or not. I think this would have to look
like a run-time fallback. Could it be structured as "return that the
page's all-visible bit is not set, instead of failing?" Or am I
confused about where the conflict is coming from?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
