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 1t8OIs-003u4u-NL for pgsql-general@arkaria.postgresql.org; Tue, 05 Nov 2024 18:29:22 +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 1t8OIp-00HEci-VG for pgsql-general@arkaria.postgresql.org; Tue, 05 Nov 2024 18:29:20 +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 1t8OIp-00HEcZ-Ji for pgsql-general@lists.postgresql.org; Tue, 05 Nov 2024 18:29:20 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t8OIm-000NFz-33 for pgsql-general@lists.postgresql.org; Tue, 05 Nov 2024 18:29:19 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-288a90e4394so2634211fac.0 for ; Tue, 05 Nov 2024 10:29:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730831355; x=1731436155; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=NQsXfWuWa18wRz8QWxakhKNthNb39VjFvj6MD0ilq10=; b=YfMHS2wItsWaibwgGZjla6Fh4SkJnFejLuuRQ3nu8b+bBO4zYPE8fi5U1/TFNvorIw cscXirqsYwUs+7OehtmNmL6aG2MtS/M+I2Hb8BtZIXlAlUZ2UQ8SfODvLHUta5EX6ZT5 xCSSkJZsrqIp7CC+SNTPTVHrCev99/vRrAZFg3n64wxsW0eysP82tyJ7fp2tVQAS83sa qgs7ZwOpESKGT2H9uG66HHMqI+DO1jYARyZaCxBWsajfc6VWCw+5nK7nkC2sFYyjtsDq aOa7ejxPMoNInPTAby07DY69AqebwQ2bHMrGLq1Ee/wUb2LQw91Rrr80I8pb7Pj14JXQ wwQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730831355; x=1731436155; h=content-transfer-encoding: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=NQsXfWuWa18wRz8QWxakhKNthNb39VjFvj6MD0ilq10=; b=DKtWDq+ogTgRPG8Brn7jAqjwI0AqrW+JXQzJXGS/3qSEGjoxQMja4J2B5gxkdvSLKC xJvtxRJtGxBglFNdbFYYCizKp+dLfseD9GIwClmL5x9tKTNfaDmeJ96/x5B1eQ6m6VmJ glv7voBsGotS3zcfZhJVh2o9FiyNkPArwDMZhVQgiSQ5N/6kpQheBy+6okXSHjHVvmoi /mMK5T+RywojIl1QuA7PUo9OalC7Wh5PZ7CHt7QlOanXIO93tnwa+SaWEYhkIFH8T1C1 xaaEHh3iI7gJaNxMdsvhThPwPsKOxDlrjPxZbVHcRGvmQX5vYq2j8PFDt/bKl0pkC5ni nngQ== X-Gm-Message-State: AOJu0YyCd/ZL4ww+5zbNFnlEXIC8QZ3HamrhAgJL+CMEydVQVLwSjzhW afpiq7zKrbFoq9JHx2vzycCDFeRYRCgz7SzWXlHl5EvHa7INtdsZdYYDSJheydWgDWm9Z1K+Lo0 MxY5ZzMIPgdt7//VeoO8IYhm/bMDhcQ== X-Google-Smtp-Source: AGHT+IGTqVfHKweccMMDWNKNnjUdEPuaegTuDhGsBW3EKYXQ9jUUlFD/EINsjY5FNkD//mY3bryQQSOHFeAh3ZqFoMQ= X-Received: by 2002:a05:6870:c094:b0:286:f7a3:a4d1 with SMTP id 586e51a60fabf-2946467a721mr20269560fac.1.1730831355338; Tue, 05 Nov 2024 10:29:15 -0800 (PST) MIME-Version: 1.0 References: <3070156.1730828552@sss.pgh.pa.us> <3075665.1730831121@sss.pgh.pa.us> In-Reply-To: <3075665.1730831121@sss.pgh.pa.us> From: Dominique Devienne Date: Tue, 5 Nov 2024 19:29:04 +0100 Message-ID: Subject: Re: Switching to NOINHERIT user triggers #XX000 error To: Tom Lane Cc: pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Nov 5, 2024 at 7:25=E2=80=AFPM Tom Lane wrote: > Dominique Devienne writes: > > On Tue, Nov 5, 2024 at 6:42=E2=80=AFPM Tom Lane wro= te: > >> This is probably a bug, at least to the extent that we don't like > >> XX000 errors to be easily reachable, so please let us know what > >> you find out. > > > Finding where the error is thrown is easy, it's when I'm doing that gra= nt. > > But the code creates two larguish schemas before that and several ROLEs= , > > so it's not easy to share. > > Really, we need a self-contained example case to do anything > about this. Maybe you could anonymize the object names in > your test? I understand, thanks. I might be able to do that. We'll see. --DD