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 1uMp3O-004dv0-48 for pgsql-general@arkaria.postgresql.org; Wed, 04 Jun 2025 14:25:18 +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 1uMp3L-00D75e-LY for pgsql-general@arkaria.postgresql.org; Wed, 04 Jun 2025 14:25:16 +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 1uMp3L-00D75V-Av for pgsql-general@lists.postgresql.org; Wed, 04 Jun 2025 14:25:15 +0000 Received: from mail-ed1-x536.google.com ([2a00:1450:4864:20::536]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uMp3I-000Bo3-08 for pgsql-general@postgresql.org; Wed, 04 Jun 2025 14:25:13 +0000 Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-606b58241c9so3514835a12.3 for ; Wed, 04 Jun 2025 07:25:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749047108; x=1749651908; darn=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=L5NCRG8ZHNc2HS+QKbQa0HwI2EVlqjNYiehIJFuglJY=; b=eqZKWA3KqIu89tffyhmMYtXfPAklHH6AlaNRfzzUaVQeWkBY41LwMLI+VE8j2X4/AE odW1LFDmOr0GLvtahKA7ohuOnjHczhBrYW5brsQx+S6W85b2ecyC5K0NKOTMNeE7jRDG ctWlG1tXDXmOdu2gpWB4uvgYhQcjtbn9VzSDvxPXBORoUjZFawOJoCVSGtBj+E9qBtd/ bFcAJeJvMJgW6qpjPJm0GJio2LyUgNtrqp5tYVqfPBvJRURzBd8H7zgpzweyD8zVvdb+ RUMRHVb+geTs8TkESN7nv19QFV8H+smK1hwOGSNReSneFKcB2XA+ZVolFeybup5sdwTx tCzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749047108; x=1749651908; 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=L5NCRG8ZHNc2HS+QKbQa0HwI2EVlqjNYiehIJFuglJY=; b=T9UUQUVmc+xvfFOQvjo/z5wYXGrZEfxUf3LN3+FQleBrF/lFbtSCU4LOgxouD7qtyT UIBgnb7DSLaWzEj4T2VQtkXfYaESvQAPZ+EZIezCwL8bnYmQ3WzC8UZh3pUxzkSjS9bS qc6aQlHh+03cP189BAR7XoTisNsJlEQ8EfPAbYzrESCG/hm2myd/x7D+zCL1sCOZZXSo +BZNtA+I6GSI7xK3l3keeizhrHYybwZTN84+HYJ3qL+JKCE5UmkJoSfqjodzqrmMLmtJ gOIlaTXhHsEczvWxaEQBZyszNM/il1d1qEyeyP2GqtV25cViBhvE5kFX9KFtHURzk1ll cmNg== X-Gm-Message-State: AOJu0Yzd/vblCNPa6tJ6u/Tnc+42Q5XTGU5wOZOavDaOzmiORRGQKMQv taZDewLMrYPprIeCHVWo4f3ZZ03xlkijRXBoEvIIK6hRhUqjXyAiZsHbQyN2F9u9c0nSKVBZ+Bf ZaBU566QvLXRaqOy9n6Hh5B3NXmRnxUOIOg== X-Gm-Gg: ASbGncuWVFNEZDdvNTlhoRvv7MWtBfseRSrd6ncnOvKe6ZT5xv88+Diyfv1ren1iD6u rEpkT41Ql3YqVLrgrw7c3tnClQ2/DGGsxjf2YPjIPN5SOe4JDsN06sz5F/b89AqSfRUnFIiHSKC c07zNT17sL9jgxLcTI4bAQoneOKIkbohEcutMbqzPz3C4= X-Google-Smtp-Source: AGHT+IGDLbDPd8sH+OU1o4iB0ZONwvSaAWv+4IpTmxajWkMK91w/p3agwv7a/PTGbAWz4YDv94ThKDb0PD40A5DAxgE= X-Received: by 2002:a17:906:ee89:b0:ad8:a935:b8ff with SMTP id a640c23a62f3a-addf8ea431emr302066566b.31.1749047108390; Wed, 04 Jun 2025 07:25:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Robert Haas Date: Wed, 4 Jun 2025 10:24:57 -0400 X-Gm-Features: AX0GCFv6h4vf7vtlpXs01qLJD7_MdZja-O7LXTy97rZQoGT3ND2gzXiqoIP2XwY Message-ID: Subject: Re: Yet more ROLE changes in v18 beta1??? To: Dominique Devienne Cc: pgsql-general@postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Dominique, Thanks for testing. This time, whatever is going wrong here is probably not my fault, because I don't think I changed anything in this area for v18. Actually, I'm unaware of anyone else having made significant changes either, but that could very easily be a case of me not paying enough attention. I think we might need to know more about what exactly happened in order to track it down. -- Robert Haas EDB: http://www.enterprisedb.com