On 1/27/13 2:32 AM, Satoshi Nagayasu wrote:
> This patch is intended to improve warning message at
> AtEOXact_Buffers(), but I guess another function,
> AtProcExit_Buffers(), needs to be modified as well. Right?
Yes, good catch. I've attached an updated patch that does the same sort
of modification to that one too.
> Then, I need some suggestion from hackers to continue this review.
> How should I reproduce this message for review?
> This is a debug warning message, so it's not easy for me
> to reproduce this message.
What I was doing to test the code out is alter this check:
if (PrivateRefCount[i - 1] != 0)
To have the opposite logic:
if (PrivateRefCount[i - 1] = 0)
Then the patch fires on every buffer, all the time. You can still tell
which are the real errors should you happen to get one, because the log
entry shows the count. If it's 0, you know that's just a debugging message.
To keep the output from a test like that from being completely
overwhelming, I also set:
shared_buffers = 16
Which is its minimum value.
--
Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com
