| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_upgrade problem with invalid indexes |
| Date: | 2012-12-07 21:37:32 |
| Message-ID: | 16450.1354916252@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Fri, Dec 7, 2012 at 04:21:48PM -0500, Tom Lane wrote:
>> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>>> Doesn't the check need to be at least indisvalid && indisready? Given
>>> that 9.2 represents !indislive as indisvalid && !indisready?
>> Um, good point. It's annoying that we had to do it like that ...
> So, does this affect pg_upgrade? Which PG versions?
I think you can just insist on indisvalid and indisready both being
true. That's okay in all releases back to 8.3.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-12-07 21:38:39 | Re: pg_upgrade problem with invalid indexes |
| Previous Message | Bruce Momjian | 2012-12-07 21:30:36 | Re: pg_upgrade problem with invalid indexes |