Обсуждение: BUG #4050: pg_dump data contains COMMIT statement (8.3, 8.4)

The following bug has been logged online:

Bug reference:      4050
Logged by:          Vladimir Kokovic
Email address:      vladimir.kokovic@a-asoft.com
PostgreSQL version: PostgreSQL 8.4
Operating system:   Linux, Kubuntu 8.04 (hardy)
Description:        pg_dump data contains COMMIT statement (8.3, 8.4)
Details:

If database contains LARGE OBJECTS pg_dump inserts COMMIT statement after
last lo_close ! Same thing is with PostgreSQL 8.3 also.

...

1\\235\\000\\000\\00001wb\\020\\000\\000\\000\\036Wj\\001\\300\\000\\000\\00
001wb\\020\\000\\000\\000\\346Wj\\001\\300\\000\\
000\\00001wb\\020\\000\\000\\000\\256Xj\\001\\300\\000\\000\\00001wb\\020\\0
00\\000\\000vYj\\001\\300\\000\\000\\00001wb\\020
\\000\\000\\000>Zj\\001\\300\\000\\000\\000');
SELECT lo_close(0);

COMMIT;

--
-- Data for Name: BLOB COMMENTS; Type: BLOB COMMENTS; Schema: -; Owner:
--


SET search_path = adefault_finansije, pg_catalog;

--
-- Name: dur_domaci_ulazni_racuni_pkey; Type: CONSTRAINT; Schema:
adefault_finansije; Owner: vlada; Tablespace:
--

ALTER TABLE ONLY dur_domaci_ulazni_racuni
    ADD CONSTRAINT dur_domaci_ulazni_racuni_pkey PRIMARY KEY (id);


...

"Vladimir Kokovic" <vladimir.kokovic@a-asoft.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