Re: [PATCH] XLogReadRecord returns pointer to currently read page
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: a.lepikhov@postgrespro.ru, hlinnaka@iki.fi, pgsql-hackers@postgresql.org
Date: 2018-11-19T01:27:29Z
Lists: pgsql-hackers
On Fri, Nov 16, 2018 at 03:23:55PM +0900, Michael Paquier wrote: > I was looking at this patch, and shouldn't we worry about compatibility > with plugins or utilities which look directly at what's in readRecordBuf > for the record contents? Let's not forget that the contents of > XLogReaderState are public. And a couple of days later, committed. I did not notice first that the comments of xlogreader.h mention that a couple of areas are private, and readRecordBuf is part of that, so objection withdrawn. There is a comment in xlog.c (on top of ReadRecord) referring to readRecordBuf which has not been removed as part of 7fcbf6a4 when WAL reading has been moved to its own facility. The original comment was from 0ffe11a. So I have removed the comment at the same time. -- Michael
Commits
-
Improve description of buffer used to store records in WAL reader
- 0999ac479292 12.0 landed
-
Remove unnecessary memcpy when reading WAL record fitting on page
- 285bd0ac4a7c 12.0 landed