Re: Legacy GiST invalid tuples - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Legacy GiST invalid tuples
Date
Msg-id 67185.1530735020@sss.pgh.pa.us
Whole thread Raw
In response to Re: Legacy GiST invalid tuples  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Legacy GiST invalid tuples
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Requiring a scan of all indexes during pg_upgrade might increase the
> upgrade time prohibitively for some sites, so I don't think that's a
> good solution.

Perhaps VACUUM could be taught to clean up invalid entries?  That
wouldn't help Andrey's unstated goal of being able to re-use the bits
for some other purpose in v12, but it might be practical to re-use
them sometime sooner than v17.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Legacy GiST invalid tuples
Next
From: Noah Misch
Date:
Subject: Re: hot_standby_feedback vs excludeVacuum and snapshots