Re: [BUG] lo_open() makes a warning/falls to an assertion

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [BUG] lo_open() makes a warning/falls to an assertion
Date: 2008-12-02 14:13:11
Message-ID: 20081202141311.GG5672@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:

> I think the solution is to have each large object have its own
> ResourceOwner, and store the snapshot in it. Otherwise the snapshot is
> left in the calling query's resowner, which is not good.

Turns out to be overkill. This patch solves the problem, by using the
transaction's resowner. I'm now going to check if we need something
similar elsewhere.

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

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2008-12-02 14:21:09 Re: PiTR and other architectures....
Previous Message Heikki Linnakangas 2008-12-02 14:11:01 Re: [PATCHES] GIN improvements