Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n09OJ-0002MF-Dd for pgsql-docs@arkaria.postgresql.org; Wed, 22 Dec 2021 21:43:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n09OI-00066w-9k for pgsql-docs@arkaria.postgresql.org; Wed, 22 Dec 2021 21:43:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n09OG-00066n-Nv for pgsql-docs@lists.postgresql.org; Wed, 22 Dec 2021 21:43:18 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n09OC-0005Dw-2P for pgsql-docs@lists.postgresql.org; Wed, 22 Dec 2021 21:43:16 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id B59625C015C; Wed, 22 Dec 2021 16:43:08 -0500 (EST) Received: from imap49 ([10.202.2.99]) by compute5.internal (MEProxy); Wed, 22 Dec 2021 16:43:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=mK0V9CKtU+XPeobU+nUhas8s9WiddAP +gpHzSk4FyFA=; b=YA9yt+fZM4Tp4gfOKbj2/2zOUwg6wEU7vovIloTJ7zM3CIX YoEUyQT/cG8n60G0mdARonz35ojflaJJBWQFz5AW9HTQ6rX9Lf0lGpKYRYirDj0L UF22gRoQqXJMK4eN2NhelWzdW3dhWNJeFBNeoCiGUPG3ZuwtWcpkEOEsr9t0nlnd bk9myfKbXNS+BSMJYw++lbjLWARq2tbgGMX7AfwTOHAytdOHtFuPIYW7R1nI6O4g QYNMxsyjIx7B3wqbcH9cGDnwm4j+NI8gPrQlmbh7208Qvbzgs2iuUVWy37IC7rgU p3pBfiTLefSDTllfatVY1hYzL8rCgmKNbkXihUw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=mK0V9C KtU+XPeobU+nUhas8s9WiddAP+gpHzSk4FyFA=; b=CYZAM+jbUBa5kbl4sSAxTy XHdjNE6Kedfv/CmTNZ0XGq/kQs06zK9Ijfzxgi4HDxoXSlVfdDs99vHHS5AjUOn5 QFK1+L0yaFi8HC9RwpXpBreLrHEYVOpyt1zoH3HVYsuOuAl2/7gkSXm/00Vf1XDc hP6XeChTkzdW3BkDiquR1JwDk2B+4bWqlksPBNmf0Z3M5TbE5in7cwHiFZrO/LBC Up2VE2SxZOTy+iX5z/6b/geJzFTb2DA88671d/4QWW5HZKIpSlvBPNU5uthRRJM9 Flhs10ujvz464hQ9KxerSYXBSS11EMqglioN8jeMQYcIvZiq8C2bRgYzS+ziOhFQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddruddtiedgudegiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrg dtreerreertdenucfhrhhomhepfdfguhhlvghrucfvrghvvghirhgrfdcuoegvuhhlvghr segvuhhlvghrthhordgtohhmqeenucggtffrrghtthgvrhhnpeejtefhuedvgffftdetve dufedtjeeuffekleevkefhveekgeelfefhjeehtdejgeenucffohhmrghinhepvghnthgv rhhprhhishgvuggsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomhepvghulhgvrhesvghulhgvrhhtohdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 60278F60074; Wed, 22 Dec 2021 16:43:08 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-4525-g8883000b21-fm-20211221.001-g8883000b Mime-Version: 1.0 Message-Id: In-Reply-To: <164007996340.19316.11169352868601919937@wrigleys.postgresql.org> References: <164007996340.19316.11169352868601919937@wrigleys.postgresql.org> Date: Wed, 22 Dec 2021 18:42:33 -0300 From: "Euler Taveira" To: vrms@netcologne.de, pgsql-docs@lists.postgresql.org Subject: Re: include_dir - 'if_exists' logic yes or no? Content-Type: multipart/alternative; boundary=42acb1aeb0bd4289ae78bc75122c5f37 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --42acb1aeb0bd4289ae78bc75122c5f37 Content-Type: text/plain On Tue, Dec 21, 2021, at 6:46 AM, PG Doc comments form wrote: > include_dir 'directory' > > it it not 100% clear whether the include_dir option also allows 'if_exists' > funtionality. > > I think a include_dir_if_exists should be possible. > If it is it should be expressed specifically in the docs. > If the functionality does not exist this should be mentioned very clear > in the docs also > There is no such directive include_dir_if_exists. Why should the documentation mention something that isn't implemented? You could suggest a new feature. IMO no documentation change is required. -- Euler Taveira EDB https://www.enterprisedb.com/ --42acb1aeb0bd4289ae78bc75122c5f37 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Tue, Dec 21,= 2021, at 6:46 AM, PG Doc comments form wrote:
include_dir 'directory'

it it not 100% clear whether the include_dir option als= o allows 'if_exists'
funtionality.

I think a include_dir_if_exists should be possible. 
    If it is it should be expressed specifically in= the docs. 
    If the functionality d= oes not exist this should be mentioned very clear
in the d= ocs also

There is no such dire= ctive include_dir_if_exists. Why should the documentation
= mention something that isn't implemented? You could suggest a new featur= e. IMO
no documentation change is required.
=

--
Euler Taveira

--42acb1aeb0bd4289ae78bc75122c5f37--