> > The comment above the query in the official documentation is rather
> > assertive
> > (even if may true to the letter) and may warrant some more cautionary
> > wording ? Added, perhaps, some variation of this:
> >
> > > For now, the only safe way to go is either reindex everything, or
> > >
On Thu, Nov 10, 2022 at 08:39:03AM -0600, Ron wrote:
> On 11/10/22 08:33, Julien Rouhaud wrote:
> > On Thu, Nov 10, 2022 at 08:04:37AM -0600, Ron wrote:
> > > On 11/10/22 02:33, Julien Rouhaud wrote:
> > > [snip]
> > > > For now, the only safe way to go is either reindex everything, or
> > > > eve
On 11/10/22 08:33, Julien Rouhaud wrote:
On Thu, Nov 10, 2022 at 08:04:37AM -0600, Ron wrote:
On 11/10/22 02:33, Julien Rouhaud wrote:
[snip]
For now, the only safe way to go is either reindex everything, or everything
except some safe cases (non-partial indexes on plain-non-collatable datatype
On Thu, Nov 10, 2022 at 08:04:37AM -0600, Ron wrote:
> On 11/10/22 02:33, Julien Rouhaud wrote:
> [snip]
> > For now, the only safe way to go is either reindex everything, or everything
> > except some safe cases (non-partial indexes on plain-non-collatable
> > datatypes
> > only). Usually, those
On 11/10/22 02:33, Julien Rouhaud wrote:
[snip]
For now, the only safe way to go is either reindex everything, or everything
except some safe cases (non-partial indexes on plain-non-collatable datatypes
only). Usually, those safe cases are usually enough to avoid most of useless
reindex activity
On Thu, Nov 10, 2022 at 11:47:01AM +0100, Karsten Hilbert wrote:
> Thanks, Julien, for your explanation.
>
> > > regarding changed collation versions this
> > >
> > > https://www.postgresql.org/docs/devel/sql-altercollation.html
> > >
> > > says:
> > >
> > > The following query can be used to
Thanks, Julien, for your explanation.
> > regarding changed collation versions this
> >
> > https://www.postgresql.org/docs/devel/sql-altercollation.html
> >
> > says:
> >
> > The following query can be used to identify all
> > collations in the current database that need to be
> >
Hi,
On Wed, Nov 09, 2022 at 12:45:17PM +0100, Karsten Hilbert wrote:
> Dear all,
>
> regarding changed collation versions this
>
> https://www.postgresql.org/docs/devel/sql-altercollation.html
>
> says:
>
> The following query can be used to identify all
> collations in the curre
Dear all,
regarding changed collation versions this
https://www.postgresql.org/docs/devel/sql-altercollation.html
says:
The following query can be used to identify all
collations in the current database that need to be
refreshed and the objects that depend on the
