Karsten Hilbert writes:
> For that matter, is DELETE FROM pg_collation ... equivalent
> to DROP COLLATION ?
There's also entries in pg_depend and pg_shdepend to worry
about.
For these built-in collations, as of v15 there are no such
entries, but prior versions had explicit "pin" entries.
Am Wed, Dec 21, 2022 at 03:46:48PM +0100 schrieb Karsten Hilbert:
> I wasn't so sure whether inserting appropriate
> rows would be equivalent to create collation...
For that matter, is DELETE FROM pg_collation ... equivalent
to DROP COLLATION ?
Thanks,
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5
Am Wed, Dec 21, 2022 at 03:41:24PM +0100 schrieb Laurenz Albe:
> I would definitely go for the backup, but here is how you can
> create these three rows in PostgreSQL v15:
>
> INSERT INTO pg_collation
> (oid, collname, collnamespace, collowner, collprovider,
> collisdeterministic, colle
On Wed, 2022-12-21 at 15:24 +0100, Karsten Hilbert wrote:
> I managed to drop the "special" collations default, C, and
> POSIX with OIDs 100, 950, 951.
>
> Is there a way to recreate them (short of restoring a backup)
> ? Naive attempts with create collation do not seem to work
> out.
I would def
Dear all,
I managed to drop the "special" collations default, C, and
POSIX with OIDs 100, 950, 951.
Is there a way to recreate them (short of restoring a backup)
? Naive attempts with create collation do not seem to work
out.
Thanks,
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F
