> I can confirm that that fixes the seg faults for me.
Thanks for confirmation.
> Did you mean you couldn't reproduce the problem in the first place, or that
> you could reproduce it and now the patch fixes it? If the first of those, I
> forget to say you do have to wait for hot standby to reach a consistency and
> open for connections, and then connect to the standby ("psql -p 9874"),
> before the seg fault will be triggered.
I meant that I was not able to reproduce the issue on HEAD.
> But, there are places where hash_xlog_vacuum_get_latestRemovedXid diverges
> from btree_xlog_delete_get_latestRemovedXid, which I don't understand the
> reason for the divergence. Is there a reason we dropped the PANIC if we
> have not reached consistency?
Well, I'm not quite sure how would standby allow any backend to
connect to it until it has reached to a consistent state. If you see
the definition of btree_xlog_delete_get_latestRemovedXid(), just
before consistency check there is a if-condition 'if
(CountDBBackends(InvalidOid) == 0)' which means
we are checking for consistent state only after knowing that there are
some backends connected to the standby. So, Is there a possibility of
having some backend connected to standby server without having it in
That is a case which should never happen, but
> it seems worth preserving the PANIC. And why does this code get 'unused'
> from XLogRecGetBlockData(record, 0, &len), while the btree code gets it from
> xlrec? Is that because the record being replayed is structured differently
> between btree and hash, or is there some other reason?
Yes, That's right. In case of btree index, we have used
XLogRegisterData() to add data to WAL record and to fetch the same we
use XLogRecGetData(). In case of hash index we have associated the
same data with some registered buffer using
XLogRegisterBufferData(0,...) and to fetch the same we use
XLogRecGetBlockData(0,...). Now, if you see XLogRecordAssemble, it
first adds all the data assciated with registered buffers into the WAL
record followed by the main data (). Hence, the WAL record in btree
and hash are organised differently.
Sent via pgsql-hackers mailing list (firstname.lastname@example.org)
To make changes to your subscription: