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 1wDIrK-002pcT-0v for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Apr 2026 09:18:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wDIrH-0052g4-0T for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Apr 2026 09:17:59 +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.96) (envelope-from ) id 1wDIrG-0052fu-0f for pgsql-hackers@lists.postgresql.org; Thu, 16 Apr 2026 09:17:58 +0000 Received: from m16.mail.163.com ([117.135.210.2]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wDIr6-00000001NfY-2yLo for pgsql-hackers@lists.postgresql.org; Thu, 16 Apr 2026 09:17:55 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Content-Type:Message-ID:Date:MIME-Version:Subject: To:From; bh=tEUoSbj6YGCKqKTHY1tIeWYBaqo06u8jVPzcaMk2USk=; b=aSWu bObrXFqwd+F1OyyXCuq3ddbblAfhwvx3GDDtXGCVnNsJ4In9c94q6vb4bRpRTE9C +p2U7FaDXKZLw6GvJZWr62ZG/Znxq0zmbAybAiYOeHZA5Mjm5tCVG6eFPwBVmH7p NRLaFsCudsqpLNoMLB9pSqTp5ik+rnGdUJUeOnA= Received: from [192.168.11.136] (unknown []) by gzga-smtp-mtada-g0-3 (Coremail) with SMTP id _____wBHqo0rqeBpTOfcFQ--.62732S2; Thu, 16 Apr 2026 17:17:32 +0800 (CST) Content-Type: multipart/alternative; boundary="------------S6q50mC02qzJkE93q4ln0DNj" Message-ID: <0e537c2a-0575-48c8-a9ac-78030f36a1ef@163.com> Date: Thu, 16 Apr 2026 17:17:24 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: docs: Fix format of CREATE FOREIGN TABLE example in postgres_fdw To: "Daniel Westermann (DWE)" , PostgreSQL Hackers References: From: Yuchen Li In-Reply-To: X-CM-TRANSID: _____wBHqo0rqeBpTOfcFQ--.62732S2 X-Coremail-Antispam: 1Uf129KBjvdXoWrtF15ZryxZrW7CrW5AF47Arb_yoWkXFcEk3 yrJr98W3yxWr4a9a15trZxArW7W3yavr1YgrWjqr12934Iv3yDXrWkZr9a9FyfC34IyFsx GrZ2qryayw4avjkaLaAFLSUrUUUUjb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUvcSsGvfC2KfnxnUUI43ZEXa7IU8FeH3UUUUU== X-Originating-IP: [123.233.246.114] X-CM-SenderInfo: 5ol13upkhqs5l126il2tof0z/xtbC9Q4IUGngqS5ExQAA3s List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------S6q50mC02qzJkE93q4ln0DNj Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 4/15/2026 5:27 PM, Daniel Westermann (DWE) wrote: > Hi, > > while reading https://www.postgresql.org/docs/devel/postgres-fdw.html > I've noticed > that there is a single bracket on one line of the CREATE FOREIGN TABLE > example. > > Browsing through other docs (e,g. > https://www.postgresql.org/docs/devel/sql-createtable.html >  ) there > doesn't seem to be a rule for that but if there is a single bracket > (e.g. CREATE TABLE distributors), the options that follow usually > start at position one and are not indented (or they follow directly > after the bracket). > > The examples in file_fdw > (https://www.postgresql.org/docs/devel/file-fdw.html) follow a mix of > options which directly follow the bracket and on a new line. > > Attached a small patch which makes it looking a bit better, at least > in my opinion. > > Regards > Daniel While looking through the patch, I noticed a small formatting issue in the following part: +) +SERVER foreign_server +OPTIONS (schema_name 'some_schema', table_name 'some_table'); The added +) line appears to have a trailing space after the closing parenthesis. Regards, Yuchen Li --------------S6q50mC02qzJkE93q4ln0DNj Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 4/15/2026 5:27 PM, Daniel Westermann (DWE) wrote:
Hi,

while reading https://www.postgresql.org/docs/devel/postgres-fdw.html  I've noticed that there is a single bracket on one line of the CREATE FOREIGN TABLE example.

Browsing through other docs (e,g. https://www.postgresql.org/docs/devel/sql-createtable.html ) there doesn't seem to be a rule for that but if there is a single bracket (e.g. CREATE TABLE distributors), the options that follow usually start at position one and are not indented (or they follow directly after the bracket).

The examples in file_fdw (https://www.postgresql.org/docs/devel/file-fdw.html) follow a mix of options which directly follow the bracket and on a new line.

Attached a small patch which makes it looking a bit better, at least in my opinion.

Regards
Daniel

While looking through the patch, I noticed a small formatting issue in
the following part:

+) 
+SERVER foreign_server
+OPTIONS (schema_name 'some_schema', table_name 'some_table');

The added +) line appears to have a trailing space after the closing
parenthesis.

Regards,
Yuchen Li

--------------S6q50mC02qzJkE93q4ln0DNj--