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 1uMoY6-004SJk-Cf for pgsql-general@arkaria.postgresql.org; Wed, 04 Jun 2025 13:52:58 +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 1uMoY4-00ClyP-DV for pgsql-general@arkaria.postgresql.org; Wed, 04 Jun 2025 13:52:57 +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 1uMoY3-00ClyH-Ty for pgsql-general@lists.postgresql.org; Wed, 04 Jun 2025 13:52:56 +0000 Received: from mail-oa1-x2b.google.com ([2001:4860:4864:20::2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uMoY2-000B85-2a for pgsql-general@postgresql.org; Wed, 04 Jun 2025 13:52:55 +0000 Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-2d4e91512b4so3717012fac.1 for ; Wed, 04 Jun 2025 06:52:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749045174; x=1749649974; darn=postgresql.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=juisaRqmj6Zs4gJuRO6jKR3IWmsHFUFWvfqp3NFKXPk=; b=BNUZoQXBZZL7XD++LH7k4c2NuAVAwNwfihqji4Dlf1QMp2rm32/m/f0CGhKoyEBIDe W4XhVfYApIEV4lvhIuttLBF0fHg+dpckQQHPTjrx2LUb4IdIe9i3EGILq6243LiCDHUf MOahwf85QSRtxK6+YQwlCvP7EL6XqZ30QtDh1xh5Dbrx0fMLi6/iCH0pcgzqtdOtZxj6 4JCrXgF9lBLAcMuGDSiX70zPSdAnX2qeRU7sHVaEDKDJFxK4lJnINul7GAKS/3w9QISr n6n307M0iDWNGqsjYYcijs0qetpGGL0jim2vrFWXNKVK7+k09EU2cwy8o6AuQ21+pR4M NuYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749045174; x=1749649974; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=juisaRqmj6Zs4gJuRO6jKR3IWmsHFUFWvfqp3NFKXPk=; b=KZG8HR9NwcPgdQLjGk4NkkV70qrv3l+PWX61ZZdR2tOE5cVDBUhZxkYo49rPuNRas3 SPShRtBq9/oGarNISLwtnOnw8qYucxrJTy44H2Qnw402Ex++oQ9zi1/pKZoiQ8HuHEHw WZbaJf6ezNwJluoH6j/fihPcUp/bfXYU4QLPgrDOyhg/tZ6VAOF2L20XZOGCXap+mzCc o9QMSD4fIJNhCbR8RjXBrGYys9VMllOxET7uyFmHoaGTkaRVZ0YChx+ICPJGjIj/1bOD EktKd80jDEAw3oEY/dl5WjgCYteS9HkID/q7PMsYBKrz3PK1rkOE4UjPu59uhZ4wN5JO pWbg== X-Gm-Message-State: AOJu0Yw4uM9NprZX3NJnhLWa7X+FM5SMeQrb9WxGne/KGaqf073GNdVn NYgBQrS79y1aR+437U7/ewi5o5ECA9mtlsBezKGiayfKHw59MSAaF5ugzu/krFCmd9+gpMd+Yll 3/38c1Od4EgdZBbRd9W0DH8H5hXzlj+foXt4O X-Gm-Gg: ASbGncuAvT6V3eyDyep3u5/8wEc+7Ir1kZgkAPiqPwcuXJgXh1/forvmQIq9WdMVMob Xw3A3DSsc+DRBO95cDsU26Hf5gFPR7hkPxOt0oMOoCqbXhBSGfu1FFsrKUSlh5COjh85mLLVoAg cmliO1jvkTdw9y9/Vg0uVeYccd583SOBZzdWw= X-Google-Smtp-Source: AGHT+IERHAo4XOmcPNeHVLPXx4vL51jfIkHwcQYhJLufifDopnhte98sqiQRjJhZf0oMbFuoyi/itXRXHU5XLyAodmM= X-Received: by 2002:a05:6871:114:b0:2b8:78c0:2592 with SMTP id 586e51a60fabf-2e9bf3d4be6mr1770516fac.23.1749045173998; Wed, 04 Jun 2025 06:52:53 -0700 (PDT) MIME-Version: 1.0 From: Dominique Devienne Date: Wed, 4 Jun 2025 15:52:42 +0200 X-Gm-Features: AX0GCFu0STgYDJ7kkVmba69TVGc4P83BlA4-j3BZxd0Yb1-qv3Rl4Xfsb2rrU9w Message-ID: Subject: Yet more ROLE changes in v18 beta1??? To: pgsql-general@postgresql.org Cc: robertmhaas@gmail.com Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk (Robert, you were kind enough to help me understand the v16 changes, so I'm hoping you might have insight on this too. And this time around, it's not one year too late I hope, since I'm testing betas now. See https://www.postgresql.org/message-id/CA%2BTgmoZMqsg6-6qN_fuMZTGu%3DVdyjv-u9ZgWbEnOTvRE450uvQ%40mail.gmail.com). Still on the subject of the recent v18 beta1 release, we're discovering new unit-test failures, on a particularly sore subject for us already, i.e. ROLE permission changes. We are still full digesting the v16+ changes, but do have swallowed already the "must have CREATEROLE *AND* ADMIN option" on the DROP'd ROLE, and that's reflected in the fact our unit test works just fine on v17 (show below, second output), and v16 (not shown). But the exact same code run against v18.0 fails. I have not even tried to analyze what's going on yet, but I certainly was not expecting new changes after the ones introduced in v16, in that area. And since the release notes are still partial (cf the "to be completed") at https://www.postgresql.org/docs/18/release-18.html, and I'm not finding anything related to ROLEs in what's there already, I wonder if someone knows how ROLE permissions changes this time around, in v18? Thanks, --DD PS: I'm not ruling out our code is at fault. Especially since we have conditional code based on the server version these days. But I'm pre-emptively asking for known changes in this area, to the experts. $ ./myruntests.csh tests_pdgm_schemas -t "..." --pq-version Connected to ... (17.4, server 18.0) Running 1 test case... unknown location(0): fatal error: in "...": #42501: ERROR: permission denied to drop role DETAIL: Only roles with the CREATEROLE attribute and the ADMIN option on role "...:ADMIN" may drop this role. *** 1 failure is detected in the test module "Master Test Suite" *** failure detail: (1) : ... failed. #42501: ERROR: permission denied to drop role DETAIL: Only roles with the CREATEROLE attribute and the ADMIN option on role "...:ADMIN" may drop this role. *** tests_pdgm_schemas in 1.790s (user: 0.290s) 52 MB $ vim .../postgres_test_config.xml $ ./myruntests.csh tests_pdgm_schemas -t "..." --pq-version Connected to ... (17.4, server 17.5) Running 1 test case... *** No errors detected *** tests_pdgm_schemas in 1.700s (user: 0.300s) 53 MB