Re: DROP COLLATION vs pg_collation question - Mailing list pgsql-general

From Laurenz Albe
Subject Re: DROP COLLATION vs pg_collation question
Date
Msg-id 26f717988471c4d672cce8c495a2c8e68446486a.camel@cybertec.at
Whole thread Raw
In response to Re: DROP COLLATION vs pg_collation question  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
Responses Re: DROP COLLATION vs pg_collation question
List 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



pgsql-general by date:

Previous
From: yudhi s
Date:
Subject: Re: Long running query causing XID limit breach
Next
From: "Shenavai, Manuel"
Date:
Subject: TOAST Table / Dead Tuples / Free Pages