diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-04-20 19:01:20 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-04-20 19:01:20 -0400 |
| commit | 9ad7e15507ffa14f51d80d6ae3ed942ea191826d (patch) | |
| tree | 9429bdff0ae2619529540132143249c62455cd70 /src/backend/parser/parse_utilcmd.c | |
| parent | 5b8e442953da0bf4950b86c7cb4a6117842aedf7 (diff) | |
| download | postgresql-9ad7e15507ffa14f51d80d6ae3ed942ea191826d.tar.gz postgresql-9ad7e15507ffa14f51d80d6ae3ed942ea191826d.zip | |
Set indcheckxmin true when REINDEX fixes an invalid or not-ready index.
Per comment from Greg Stark, it's less clear that HOT chains don't conflict
with the index than it would be for a valid index. So, let's preserve the
former behavior that indcheckxmin does get set when there are
potentially-broken HOT chains in this case. This change does not cause any
pg_index update that wouldn't have happened anyway, so we're not
re-introducing the previous bug with pg_index updates, and surely the case
is not significant from a performance standpoint; so let's be as
conservative as possible.
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions