Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qoNVj-0013kS-4q for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Oct 2023 12:31:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qoNVg-00Cxjp-Gu for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Oct 2023 12:31:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qoNVg-00CxjB-6Z for pgsql-hackers@lists.postgresql.org; Thu, 05 Oct 2023 12:31:21 +0000 Received: from mail-wr1-x42a.google.com ([2a00:1450:4864:20::42a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qoNVa-000AZI-0L for pgsql-hackers@lists.postgresql.org; Thu, 05 Oct 2023 12:31:20 +0000 Received: by mail-wr1-x42a.google.com with SMTP id ffacd0b85a97d-323168869daso931603f8f.2 for ; Thu, 05 Oct 2023 05:31:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696509073; x=1697113873; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=bkwNVniIn5+B9kFgftXRr/+i+oUN7bAhP6C4xRQUsVc=; b=Bh0kJQq/WW/Z9BsCfMteRvveMwB1Cn+/IEidl6AH6xmTSraV2owDwW1zpub/v92ZdU 9nZzI3mRIq2icC384f6XjC8HXemIgKg7LH0IKXyw+AnKC31zgbgiwG3yRKlnRXtHgQTh eEtibzaSE1mq8BFya8ZMqdBuE1oIWA5kCv9tR2EJKgh0cnOPb7cATa42PqeY6BIdFRON pUKZxa9XHZR8FijSlqSmNZlYbQpDY+05AtV8r/3yoTDTsBhvgeoIoXmXBZg2LOjNMd4L IpYEo49CaQFDRlyJRTutuuw/frMGY3i0s46HTu1gtg/eI65s5GNdp5Xkb72ou630meMC cdSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696509073; x=1697113873; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=bkwNVniIn5+B9kFgftXRr/+i+oUN7bAhP6C4xRQUsVc=; b=C0AEhvitELGwYWiYUwB8PhPHOcY8V2uNqwABrXBIUzKb54uvp9IkUPVzaBSOhonY7P hpkHv5RcGWDQ0DI5ZCVJKjhri98nTnVkPQafGL084GKtr4pMkt6N1BqK1TPjk3h7abZB DXnvE7kay501v854KXbKIJyhD2EOYEp5hdQJ/n54Cx7dmuaawDD5YDlFUbYUPolGQM3a 1hESd5YBNEaaEF3CdubkrY/U1GCTopC0of0yX+xFUUehHVNcyrBjjgMlt6kK9re6asDi KcmUxliOEKXbj3gKFxWC6lAHM/qQjVT1/SFqkZInJHTHjd9IL+3ww3bh/RmfzJ6IWH3Q ekWw== X-Gm-Message-State: AOJu0Yx14lWIfHXHZMqwyyAgqc/M/UBrH1DLCFllOyGp3Cu+zHiy28IX 9tchzULJki89oOoMe3DKBH/RWzWa8thnSrwPucc= X-Google-Smtp-Source: AGHT+IFS2UcoSt5CZCekbgf0cBPdtJvjcrnH7OzTVRvQr/vpTjc2qLJ3aZ2dqBZiBS30FipYXJX91kUilmrfN0XYT0k= X-Received: by 2002:a5d:538b:0:b0:319:67ac:4191 with SMTP id d11-20020a5d538b000000b0031967ac4191mr4342309wrv.37.1696509072520; Thu, 05 Oct 2023 05:31:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Matthias van de Meent Date: Thu, 5 Oct 2023 14:31:00 +0200 Message-ID: Subject: Re: Change of behaviour for creating same type name in multiple schemas To: Dave Cramer Cc: PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 5 Oct 2023 at 14:13, Dave Cramer 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