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.96) (envelope-from ) id 1wPbOK-000ssr-1c for pgsql-hackers@arkaria.postgresql.org; Wed, 20 May 2026 07:30:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wPbOG-006g96-2y for pgsql-hackers@arkaria.postgresql.org; Wed, 20 May 2026 07:30:53 +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.96) (envelope-from ) id 1wPbOG-006g8x-24 for pgsql-hackers@lists.postgresql.org; Wed, 20 May 2026 07:30:53 +0000 Received: from udcm-wwu2.uni-muenster.de ([128.176.118.28]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wPbOE-00000000SAa-3t3Z for pgsql-hackers@lists.postgresql.org; Wed, 20 May 2026 07:30:52 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uni-muenster.de; i=@uni-muenster.de; q=dns/txt; s=uniout; t=1779262251; x=1810798251; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=OMafnvKzSujXMEDctpcF/qmMImU3B/M/eDqKQUL9iTU=; b=ObuSgYeo8cxHz7rumjadSZwqSY2RP0XTmaBBTo3n8XKGe8+72BRlgshU 3jwvlHRw5KKvo0UWvuhvukcVv38uDJERYphfjoPxPhVrZYJbh/BNc85Uj NutCd2kXuA6c344jsg2GxI8ynlrPhB6Et8nfehlHVWJn6DaD6eVqmudxO 8UT4VHPDRLH9G++yqhSS9gYdjeqP7gBhiYaY4t/3C/XNdyJKdkHFWrj3m 7WBiNWOY7wfEN9fNrwWMStwBqklfoqjaPsQmL0W6WoVrRxCbqq5kEhAfK KtQu9dHXge9V6rdlhhionnbM2FTPOEWBrKJO36Ht2byda/2kSpnR+XoCN g==; X-CSE-ConnectionGUID: z4zJLO5/QZaxL8KlkdwlEA== X-CSE-MsgGUID: +QuiohTYSli8SkGNc3SdTw== X-IronPort-AV: E=Sophos;i="6.23,243,1770591600"; d="scan'208";a="394701893" Received: from secmail.uni-muenster.de ([128.176.118.4]) by UDCM-RELAY2.UNI-MUENSTER.DE with ESMTP; 20 May 2026 09:30:50 +0200 Received: from [192.168.178.49] (dynamic-077-177-151-182.77.177.pool.telefonica.de [77.177.151.182]) by SECMAIL.UNI-MUENSTER.DE (Postfix) with ESMTPSA id 6921D20ADF02; Wed, 20 May 2026 09:30:49 +0200 (CEST) Message-ID: <6071d0a2-a02d-4fb8-bdec-1991411d4a9d@uni-muenster.de> Date: Wed, 20 May 2026 09:30:48 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: PSQL - prevent describe listing tables that are already in listed schemas To: Nisha Moond , Peter Smith Cc: PostgreSQL Hackers References: <5420ddcb-7b55-4a73-b8c5-3602abfac78b@uni-muenster.de> <1b1c88ce-2c61-4faf-b647-496525fc177f@uni-muenster.de> Content-Language: en-US, de-DE From: Jim Jones In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Nisha On 20/05/2026 09:09, Nisha Moond wrote: > For the describePublications (\dRp+) case, should we add an (sversion >> = 150000) guard around the new change, since it accesses > pg_publication_namespace, which is only available in PG15 and above? > Thoughts? I considered that in my first review, but since PG14 will be EOL'd by the time PG20 is shipped, I thought it wouldn't be necessary. Thanks! Best, Jim