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 1lmGyJ-0008BD-CF for pgsql-docs@arkaria.postgresql.org; Thu, 27 May 2021 14:26:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lmGyI-0004Vb-Ak for pgsql-docs@arkaria.postgresql.org; Thu, 27 May 2021 14:26:50 +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 1lmGyI-0004VT-4v for pgsql-docs@lists.postgresql.org; Thu, 27 May 2021 14:26:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lmGyG-0004do-8a for pgsql-docs@lists.postgresql.org; Thu, 27 May 2021 14:26:49 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 14REQj9H1718746; Thu, 27 May 2021 10:26:45 -0400 From: Tom Lane To: "tanghy.fnst@fujitsu.com" cc: Bruce Momjian , "pgsql-docs@lists.postgresql.org" , Michael Paquier Subject: Re: pg_type_d.h location incorrect In-reply-to: References: <162149020918.26174.7150424047314144297@wrigleys.postgresql.org> <1424852.1621999180@sss.pgh.pa.us> <1681252.1622080694@sss.pgh.pa.us> Comments: In-reply-to "tanghy.fnst@fujitsu.com" message dated "Thu, 27 May 2021 06:13:36 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1718744.1622125605.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 27 May 2021 10:26:45 -0400 Message-ID: <1718745.1622125605@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "tanghy.fnst@fujitsu.com" writes: > On Thursday, May 27, 2021 10:58 AM, Tom Lane wrote >> So I ended up with the attached --- what do you think? > The doc-fix LGTM. = > But I couldn't apply the patch at HEAD(2941138e60). Maybe you did the fi= x at a branch other than HEAD? No ... "patch -p1 <~/improve-pgservice-docs.patch" works fine for me. >> Also, looking at this, I note that "~/.pg_service.conf" is still a >> platform-ism. We could make that slightly better by writing >> "$HOME/.pg_service.conf", but is that good enough? > Agreed. Besides, A lot of places in current Doc have been useing ~/.pg_*= ** already. > IMHO, it's good to keep the consistency. Oh, good point ... grepping finds lots of occurrences of '~/' and only one of '$HOME/'. Seems like we ought to change that one: $ grep -r 'HOME/' . ./config.sgml: This writes out files to $HOME/.debug/jit/= ; the regards, tom lane