Re: DROP COLLATION vs pg_collation question

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: DROP COLLATION vs pg_collation question
Date: 2024-06-13 07:49:46
Message-ID: 26f717988471c4d672cce8c495a2c8e68446486a.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2024-06-12 at 21:13 +0200, Karsten Hilbert wrote:
> > Note that with DROP COLLATION you can only remove collations
> > that belong to the encoding of your current database.
>
> A-ha !  Can that bit be found anywhere in the docs ?

src/backend/catalog/namespace.c:

/*
* get_collation_oid - find a collation by possibly qualified name
*
* Note that this will only find collations that work with the current
* database's encoding.
*/
Oid
get_collation_oid(List *collname, bool missing_ok)

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Shenavai, Manuel 2024-06-13 07:55:02 TOAST Table / Dead Tuples / Free Pages
Previous Message yudhi s 2024-06-13 07:43:06 Re: Long running query causing XID limit breach