Re: 7.4.5 losing committed transactions - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: 7.4.5 losing committed transactions
Date
Msg-id 4154CAAE.3010000@Yahoo.com
Whole thread Raw
In response to Re: 7.4.5 losing committed transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 7.4.5 losing committed transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 9/24/2004 6:37 PM, Tom Lane wrote:

> Can you still reproduce the problem if you take out the ereport call
> in quickdie()?

Will check ...

> 
> BTW, what led you to develop this test setup ... had you already seen
> something that made you suspect a data loss problem?

Good guess ... what actually happenend was that after a couple of these 
getaddrinfo() SIGSEGV's on AIX, one of our Slony-replica was out of 
sync. Long story short, it all didn't make sense.

Now the scary thing is that not only did this crash rollback a committed 
transaction. Another session had enough time in between to receive a 
NOTIFY and select the data that got rolled back later.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 7.4.5 losing committed transactions
Next
From: "Francisco Figueiredo Jr."
Date:
Subject: Parse message problem, maybe a bug?