On 07/08/2013 04:59 PM, Tom Lane wrote: > Alvaro Herrera <alvhe...@2ndquadrant.com> writes: >> Well, Tom opined in >> http://www.postgresql.org/message-id/23249.1370878...@sss.pgh.pa.us that >> the current patch is okay. I have a mild opinion that it should instead >> print only SHR_LOCK when both bits are set, and one of the others when >> only one of them is set. But I don't have a strong opinion about this, >> and since Tom disagrees with me, feel free to exercise your own (Jeff's) >> judgement. > > FWIW, I think that's exactly what I did in the preliminary 9.3 patch > that I committed to pg_filedump a few weeks ago. Could you take a look > at what's there now and see if that's what you meant?
So, is this getting committed today, or do we bounce it? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
