| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Preventing index scans for non-recoverable index AMs |
| Date: | 2008-12-17 23:14:31 |
| Message-ID: | 1229555671.4793.156.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2008-12-17 at 18:01 -0500, Jaime Casanova wrote:
> On Wed, Dec 17, 2008 at 5:54 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
> > We don't yet have a mechanism for an
> > index AM to say "damn, this index is screwed up, don't use it".
> >
>
> mark pg_index.indisvalid and/or pg_index.indisready to false in the
> hot standby node?
We can't edit the database until recovery is over, so that doesn't help
us while in recovery mode. So not an option.
It doesn't help us after recovery mode either because there is no
infrastructure (yet) for an index AM's rmgr to exact a transaction after
completion of recovery. So yes, that is the way it will be done, but
there is a non-trivial effort to allow it to happen.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2008-12-17 23:15:12 | Re: Variadic parameters vs parameter defaults |
| Previous Message | Kenneth Marshall | 2008-12-17 23:12:52 | Re: Preventing index scans for non-recoverable index AMs |