Postgres Pro
Downloads
Home   >   mailing lists

Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6
Date
Msg-id 26918.1394673323@sss.pgh.pa.us
Whole thread Raw
In response to 9a57858f1103b89a5674f0d50c5fe1f756411df6  (Robert Haas <robertmhaas@gmail.com>)
Responses Bug: Fix Wal replay of locking an updated tuple (WAS: Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6)  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Tree view 
Robert Haas <robertmhaas@gmail.com> writes:
> Discuss.

This thread badly needs a more informative Subject line.

But, yeah: do people think the referenced commit fixes a bug bad enough
to deserve a quick update release?  If so, why?  Multiple reports of
problems in the field would be a good reason, but I've not seen such.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: db_user_namespace a "temporary measure"
Next
From: "Joshua D. Drake"
Date:
Subject: Bug: Fix Wal replay of locking an updated tuple (WAS: Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6)