Merlin Moncure <mmonc...@gmail.com> writes:
> On Wed, Oct 19, 2011 at 6:04 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> ProcessStandbyHSFeedbackMessage has a race condition: it thinks it can
>> call GetOldestXmin and then the result will politely hold still while
>> it considers what to do next.
> curious: are these bugs in production, and what would be the user
> visible symptoms of seeing them in the wild?
There's no bug so far as data integrity on the master goes. The risk
is that you'd see queries failing with replication conflicts on a
hot-standby slave even though you thought you'd protected them by
setting hot_standby_feedback = on. That would happen if any rows
actually got vacuumed despite the standby's attempt to set an xmin
that would protect them. This is possible anyway at walsender
startup, but I think the logic errors made it more probable.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
