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

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