Re: SPITupleTable members missing in docs

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-docs@lists.postgresql.org, Michael Paquier <michael@paquier.xyz>
Date: 2019-07-17T11:55:56Z
Lists: pgsql-docs

Attachments

> On 15 Jul 2019, at 23:18, Fabien COELHO <coelho@cri.ensmp.fr> wrote:

>> I quite like this suggestion, so I’ve changed the patch to do this.  Removed
>> the doc: in the commit message to indicate that this is no longer just touching
>> documentation.
> 
> About v2: applies cleanly, compiles, make check and doc gen ok.
> 
> However, the documentation does not look right, field comments are not aligned. Do not use tabs in the sgml file, use spaces only, otherwise the display layout is left to chance.

Of course, that was me fat-fingering.  Fixed in the attached v3.  Thanks for
reviewing!

cheers ./daniel

Commits

  1. Clarify the distinction between public and private SPITupleTable fields.

  2. Prevent leakage of SPI tuple tables during subtransaction abort.