Re: snapshot leak and core dump with serializable transactions - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: snapshot leak and core dump with serializable transactions
Date
Msg-id 2e78013d0812030907ob9cc327t1131997770308a30@mail.gmail.com
Whole thread Raw
In response to Re: snapshot leak and core dump with serializable transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: snapshot leak and core dump with serializable transactions  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
<br /><br /><div class="gmail_quote">On Wed, Dec 3, 2008 at 7:42 PM, Tom Lane <span dir="ltr"><<a
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span>wrote:<br /><blockquote class="gmail_quote"
style="border-left:1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br
/><br/></div>That's absolutely wrong.  It'll complain about whatever snapshots the<br /> owners still hold.<br /><br
/></blockquote></div><br/>You must be right; I don't understand that code much. But don't we expect the snapshots to be
cleanlyreleased at that point and if not we flash warnings anyways ? AtEOXact_Snapshot only unregisters the serialized
snapshotwhich otherwise release resource owner will complain about.<br /><br clear="all" />Thanks,<br />Pavan<br /><br
/>--<br />Pavan Deolasee<br />EnterpriseDB     <a href="http://www.enterprisedb.com">http://www.enterprisedb.com</a><br
/>

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Visibility map, partial vacuums
Next
From: Gregory Stark
Date:
Subject: Re: Visibility map, partial vacuums