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 1uMpAy-004gzY-Aq for pgsql-general@arkaria.postgresql.org; Wed, 04 Jun 2025 14:33:08 +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 1uMpAw-00DEFY-A6 for pgsql-general@arkaria.postgresql.org; Wed, 04 Jun 2025 14:33:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uMpAv-00DEFQ-Sw for pgsql-general@lists.postgresql.org; Wed, 04 Jun 2025 14:33:06 +0000 Received: from mail-oa1-x2f.google.com ([2001:4860:4864:20::2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uMpAu-000BQ3-2P for pgsql-general@postgresql.org; Wed, 04 Jun 2025 14:33:05 +0000 Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-2da3c572a0bso3581572fac.3 for ; Wed, 04 Jun 2025 07:33:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749047584; x=1749652384; darn=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=pCRsHKS1FSII98o06AgQoFhQW9ULjk4RwGW5BlcnB+0=; b=eKEiyhI0U4TnOIOuIhHW5MS5C1P6sZqzx5PL3IpsL3NzR0JofGgRRmttvtGWnBCGif I7D2Xs2BK4V8n7dWa7y/V/H5TQZIQD7F7ZWAO/4MQdaFL59lHerYKJxHWjcgTlkU6W0U foc38nYDry65OnSRmzu2/5jAYtWAVRrZTTNvI5HawDrdsoe6UjFugLglZ2mZTXDiIdaD PZ2JCyUW/kHb1MPmtDDPkAG/xpTTFv6BV07qSDzVQ1ZtZPqwcZtBbz2Yd8RqbZixW8mz x85yzF3khYN79KXP/yH1P57sf3294U7W38AW4R4jIotSfnojPZebVMw5BT4uke/ruSFU INBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749047584; x=1749652384; 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=pCRsHKS1FSII98o06AgQoFhQW9ULjk4RwGW5BlcnB+0=; b=PJ+kAu5bFDR17HpRevQUzPU+TRXb7Vr9FG7dbWRvvh8qo4DFwOEi9Ipz5HwISbdpNL vgE9WBNUc7j6WZHHC34SzDilE6QWZ6+hWIS21s640qWnFDRii6H35endYNquEPnm0vah 7dD0VAyZV/HhphjM1DjTbFUHxclO/4RZz1fkKXObohOZaGeAwsd0b2fWrG4zajqEK5fx nSQ8zDlIRyF3R+2sRJ1wUbyYkN4Yw9cNRe3GJlSHDZCvkWq6O+UVdof436sQ3BcQ1QOG dD1yrWclqsfId85na9/QEtwNHlOoNxm6TjCYaJ00mF1u9dUaNQyrfiX5DQIehHaLZ0JS q8zQ== X-Gm-Message-State: AOJu0YzhQQUgjjwRCmdaXUSwKFfGI4yNhkpBfOmxD88QgeSZKJXmMs8I bsAHISw1GEmbWzekk+YJlYtm9GhCXUhalIjYcvsO70vZGK3BCbzE6IaOt0Svl7Pi3n5UAvChCPP xpETEZueKH8hJR2AQEWIcx1HAtH+k6Ug= X-Gm-Gg: ASbGnctK/9HCK/i5RPmmL95Gief0B32enqXQiBtCRyEw+vgYWvU2GZ7FAUUGizHoPQA e7ZRzGE8MvkWNmJ0VMryhPNMi7IsbgtHatYgneGUliUcpAyfF2ZcB9iRI8V98KKEJy64vxsgvVN R5fkcdnS0j/u2yHTG40y9PgysEyeKgZ0oe9AoZr6TizERBmg== X-Google-Smtp-Source: AGHT+IHybpEkhHhPbH8MHYtz8RPIYSoyLwp7pxslauFO2b+vE8LkFz87M2B2Ve8sjOugUPUL++uevECtl2zTOkBQgaU= X-Received: by 2002:a05:6870:3c14:b0:2cb:c780:ac52 with SMTP id 586e51a60fabf-2e9bf4d35b3mr1993473fac.23.1749047583868; Wed, 04 Jun 2025 07:33:03 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dominique Devienne Date: Wed, 4 Jun 2025 16:32:52 +0200 X-Gm-Features: AX0GCFtKItGWAqBWkvadCbhZAJkZuY-P71LXcff5217zsiRSZXKKSsXm7W0bMNc Message-ID: Subject: Re: Yet more ROLE changes in v18 beta1??? To: Robert Haas Cc: pgsql-general@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 Wed, Jun 4, 2025 at 4:25=E2=80=AFPM Robert Haas = wrote: > Hi Dominique, Hi Rober, > 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. OK, good to know. And thanks for the quick answer. Unfortunately, digging into this is not something I can do right away. v18 is still a few months out, I do hope I can investigate before that. In any case, if anyone else knows about changes in this area, I'm intereste= d. Thanks, --DD