From: Michael Paquier <michael@paquier.xyz>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: SPITupleTable members missing in docs
Date: Mon, 17 Jun 2019 11:10:29 +0900
Message-ID: <20190617021029.GH3153@paquier.xyz> (raw)
In-Reply-To: <FF46808A-4B7B-4B48-B265-0707991C6970@yesql.se>
References: <0D19F836-B743-4340-B6A2-F148CA3DD1F0@yesql.se>
<5148.1560521723@sss.pgh.pa.us>
<FF46808A-4B7B-4B48-B265-0707991C6970@yesql.se>
On Fri, Jun 14, 2019 at 04:40:51PM +0200, Daniel Gustafsson wrote:
> Yeah, that’s clearly an alternative. If we go down this route, then perhaps
> the docs should be swept for other instances (if any) and handle them all to
> keep things consistent? (and yes, I volunteer if we want to opt for that.)
FWIW, we still need a proper description of these fields in the docs,
so listing them in spi.sgml has the advantage to improve the grepping
coverage of which area needs to be patched. This structure not
updated actually shows that this argument can be wrong as well ;p
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: michael@paquier.xyz, daniel@yesql.se, tgl@sss.pgh.pa.us, pgsql-docs@lists.postgresql.org
Subject: Re: SPITupleTable members missing in docs
In-Reply-To: <20190617021029.GH3153@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox