pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: pgsql-general@lists.postgresql.org
Subject: Q: fixing collation version mismatches
Date: Sun, 13 Nov 2022 21:45:32 +0100
Message-ID: <Y3FXbJiKcp04HEER@hermes.hilbert.loc> (raw)

Dear all,

just to confirm my understanding:

Is it correct to say that the following sequence will "fix"
all current collation version issues in a given database ?

	REINDEX DATABASE db_in_question;
	ALTER DATABASE db_in_question REFRESH COLLATION VERSION;
	ALTER COLLATION every_collation_from_pg_collation REFRESH VERSION;

Note that I am currently _not_ concerned with minimizing
work by running this on objects only that really need a
reindex/refresh.

Thanks,
Karsten
--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B





view thread (7+ messages)  latest in thread

Message-ID: <Y3FXbJiKcp04HEER@hermes.hilbert.loc>
Permalink:  ../Y3FXbJiKcp04HEER@hermes.hilbert.loc/
Also on:    postgresql.org/message-id/Y3FXbJiKcp04HEER@hermes.hilbert.loc

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: Karsten.Hilbert@gmx.net
  Subject: Re: Q: fixing collation version mismatches
  In-Reply-To: <Y3FXbJiKcp04HEER@hermes.hilbert.loc>
  References: <Y3FXbJiKcp04HEER@hermes.hilbert.loc>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox