Bug: Fix Wal replay of locking an updated tuple (WAS: Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6)

On 03/12/2014 06:15 PM, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Discuss.
>
> This thread badly needs a more informative Subject line.
>

No kidding. Or at least a link for goodness sake. Although the 
pgsql-packers list wasn't all that helpful either.

What I know is that we have a known in the wild version of PostgreSQL 
that eats data. That is bad. It is unfortunate that we just released 
9.3.3 but we can't knowingly allow people to get their data eaten. We 
look bad.

It appears that this is the specific bug:

http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=9a57858f1103b89a5674f0d50c5fe1f756411df6

JD


-- 
Command Prompt, Inc. - http://www.commandprompt.com/  509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms   a rose in the deeps of my heart. - W.B. Yeats