Alvaro Herrera wrote: > KaiGai Kohei wrote: > > > -- (3) tries to open it with writable mode under transaction block. > > postgres=# BEGIN; > > BEGIN > > postgres=# SELECT lo_open(24576, x'40000'::int); > > WARNING: Snapshot reference leak: Snapshot 0x96b8488 still referenced
> I'm investigating now. Thanks for the report. 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. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
