Stephen Frost <sfr...@snowman.net> writes: > * Andrew Dunstan (and...@dunslane.net) wrote: >> Making the user fix it seems much more sensible to me. Otherwise I >> suspect we'll find users who get strangely surprised when they can >> no longer find any trace of an expected index in their upgraded >> database.
> Or preserve it as-is. To do that, we would have to add an option to CREATE INDEX to create it in an invalid state. Which is stupid... 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