Postgres Pro
Downloads
Home   >   mailing lists

Re: Change of behaviour for creating same type name in multiple schemas - Mailing list pgsql-hackers

From Matthias van de Meent
Subject Re: Change of behaviour for creating same type name in multiple schemas
Date
Msg-id CAEze2WgVauSMS4CyABgotq7L--AU-YmtFsx1vA=+n81RsvGF_Q@mail.gmail.com
Whole thread Raw
In response to Change of behaviour for creating same type name in multiple schemas  (Dave Cramer <davecramer@gmail.com>)
List pgsql-hackers
Tree view 
On Thu, 5 Oct 2023 at 14:13, Dave Cramer <davecramer@gmail.com> wrote:
>
> Greetings,
>
> Before 16 if I created an array type in schema1 it would be named schema1._array_type
> if I created the same type in schema 2 it would have been named
>
> schema2.__array_type
>
> Can someone point me to where the code was changed ?

This was with commit 70988b7b [0] in July 2022, based on this thread
[1] (moved from -bugs).

Kind regards,

Matthias van de Meent
Neon (https://neon.tech)

[0] https://github.com/postgres/postgres/commits/70988b7b0a0bd03c59a2314d0b5bcf2135692349
[1] https://www.postgresql.org/message-id/flat/b84cd82c-cc67-198a-8b1c-60f44e1259ad%40postgrespro.ru

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Add a new BGWORKER_BYPASS_ROLELOGINCHECK flag
Next
From: Robert Haas
Date:
Subject: Re: pgBufferUsage.blk_{read|write}_time are zero although there are pgBufferUsage.local_blks_{read|written}