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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: snapshot leak and core dump with serializable transactions
Date: 2008-12-03 19:45:01
Message-ID: 20081203194501.GK3968@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera escribió:

> Yeah, we need two "at-commit" routines, one of which needs to be called
> early. I'm prepping a patch.

Here it is ... the large object patch is also included. I've created
new functions to specify the resource owner to register a snapshot in;
now that there are two callers, it seems likely that there will be more
in the future.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment Content-Type Size
lobj-snapshot-4.patch text/x-diff 8.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-12-03 20:04:27 pgsql: Properly unregister OpenSSL callbacks when libpq is done with
Previous Message Alvaro Herrera 2008-12-03 19:32:18 Re: snapshot leak and core dump with serializable transactions