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

From Heikki Linnakangas
Subject Re: snapshot leak and core dump with serializable transactions
Date
Msg-id 4936EA20.4070300@enterprisedb.com
Whole thread Raw
In response to Re: snapshot leak and core dump with serializable transactions  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: snapshot leak and core dump with serializable transactions
List pgsql-hackers
Alvaro Herrera wrote:
> 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.

I'm surprised you implemented RegisterSnapshotOnOwner by switching 
CurrentResourceOwner and calling RegisterSnapshot, rather than 
implementing RegisterSnapshot by calling RegisterSnapshotOnOwner(..., 
CurrentResourceOwner).

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Re: [BUGS] libpq does not manage SSL callbacks properly when other libraries are involved.
Next
From: "Robert Haas"
Date:
Subject: Re: Simple postgresql.conf wizard