On Tue, May 03, 2016 at 11:13:54PM -0400, Tom Lane wrote:
> Noah Misch writes:
> > Commit bb14050 said:
> > - change order for tsquery, so, users, who has a btree index over
> > tsquery,
> > should reindex it
>
> We undid that in 1ec4c7c05, no?
Ah, looks that way.
> > Commit 61d66c4
Noah Misch writes:
> Commit bb14050 said:
> - change order for tsquery, so, users, who has a btree index over tsquery,
> should reindex it
We undid that in 1ec4c7c05, no? (Even if we didn't, the usefulness
of a btree index on tsquery seems negligibly small.)
> Commit 61d66c4 may or ma
Commit bb14050 said:
- change order for tsquery, so, users, who has a btree index over tsquery,
should reindex it
The last change of this sort also modified pg_upgrade to issue REINDEX
guidance. See old_8_3_invalidate_hash_gin_indexes() in the PostgreSQL 9.4
source. PostgreSQL 9.6 pg_
