Re: snapshot leak and core dump with serializable transactions

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: snapshot leak and core dump with serializable transactions
Date: 2008-12-03 12:52:32
Message-ID: 20081203125232.GB3968@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pavan Deolasee escribió:

> 2. In CommitTransaction(), I think we should call AtEOXact_Snapshot *before*
> releasing the resource owners. Otherwise, ResourceOwnerReleaseInternal
> complains about snapshot leak and then forcefully unregisters the snapshot.
> Later when AtEOXact_Snapshot is called, it again tries to unregister the
> serializable snapshot and assertion fails.

Hmm, I've been wondering if we can get away with not having
AtEOXact_Snapshot at all.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-12-03 12:58:28 Re: maintenance memory vs autovac
Previous Message Peter Eisentraut 2008-12-03 12:49:15 pg_get_keywords descriptions