Skip site navigation (1) Skip section navigation (2)

Re: BUG #4050: pg_dump data contains COMMIT statement (8.3, 8.4)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Vladimir Kokovic" <vladimir(dot)kokovic(at)a-asoft(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4050: pg_dump data contains COMMIT statement (8.3, 8.4)
Date: 2008-03-22 20:13:03
Message-ID: 3342.1206216783@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Vladimir Kokovic" <vladimir(dot)kokovic(at)a-asoft(dot)com> writes:
> If database contains LARGE OBJECTS pg_dump inserts COMMIT statement after
> last lo_close ! Same thing is with PostgreSQL 8.3 also.

Well, sure.  It matches the BEGIN before the first lo_open.  Without
those blob-restoring wouldn't work at all.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2008-03-22 23:49:46
Subject: Re: BUG #3983: pgxs files missing from binary installation
Previous:From: Vladimir KokovicDate: 2008-03-22 19:04:32
Subject: BUG #4050: pg_dump data contains COMMIT statement (8.3, 8.4)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group