From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
---|---|
To: | Dave Cramer <davecramer(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Change of behaviour for creating same type name in multiple schemas |
Date: | 2023-10-05 12:31:00 |
Message-ID: | CAEze2WgVauSMS4CyABgotq7L--AU-YmtFsx1vA=+n81RsvGF_Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 5 Oct 2023 at 14:13, Dave Cramer <davecramer(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2023-10-05 12:51:40 | Re: pgBufferUsage.blk_{read|write}_time are zero although there are pgBufferUsage.local_blks_{read|written} |
Previous Message | Bharath Rupireddy | 2023-10-05 12:21:31 | Re: Add a new BGWORKER_BYPASS_ROLELOGINCHECK flag |