Re: SPITupleTable members missing in docs

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Daniel Gustafsson <daniel@yesql.se>, pgsql-docs@lists.postgresql.org, Michael Paquier <michael@paquier.xyz>
Date: 2019-07-15T13:33:24Z
Lists: pgsql-docs
Fabien COELHO <coelho@cri.ensmp.fr> writes:
> Hello Daniel,
>> 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.

> And it should be posted to <pgsql-hackers@lists.postgresql.org>.

Seems excessive, since there's no actual functional change here.

			regards, tom lane



Commits

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

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