Robert Haas <> writes:
> Well, it's sounding like we can only display the whole tuple if (1)
> the message level is less than ERROR and (2) the snapshot is an MVCC
> snapshot.  That's an annoying and hard-to-document set of limitations.
>  But we should be able to display the TID always, so I think we should
> drop the part of the patch that tries to show tuple data and revisit
> that in a future release if need be.

+1.  That avoids the thing that was really bothering me about this
patch, which is that it seemed likely to create a whole new set of
failure modes.  Every case in which the data-printing effort could
fail is a case where the patch makes things *less* debuggable, not
more so.

                        regards, tom lane

Sent via pgsql-hackers mailing list (
To make changes to your subscription:

Reply via email to