Re: [BUG] lo_open() makes a warning/falls to an assertion - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [BUG] lo_open() makes a warning/falls to an assertion
Date
Msg-id 26676.1228266247@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUG] lo_open() makes a warning/falls to an assertion  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: [BUG] lo_open() makes a warning/falls to an assertion
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> 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.

That's not gonna scale to transactions that touch lots of large objects
(think pg_dump).  Also it seems like it would be arbitrarily altering
the past behavior of LOs.  Why don't they just use the calling query's
snapshot (which I think is what the historical behavior is, though I'm
too lazy to check right now)?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: maintenance memory vs autovac
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] GIN improvements