Re: pg_dump and insert multi-rows option

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Cédric Villemain <cedric(dot)villemain(at)dalibo(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump and insert multi-rows option
Date: 2007-09-04 17:22:01
Message-ID: 27494.1188926521@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

=?iso-8859-15?q?C=E9dric_Villemain?= <cedric(dot)villemain(at)dalibo(dot)com> writes:
> Well, I can only make a new ask.
> Why is there the --inserts and --attribute-inserts options ?

It's mostly historical IMHO. The COPY option used to have bugs for
corner cases like inheritance child tables that had been ALTERed after
creation. That's all gone now. The only reason I can see to use
these options today is if you want to try to port the dump to some
other database ... and in that case you probably shouldn't assume
multi-insert will work anyway.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian G. Pflug 2007-09-04 17:22:44 Lazy xid assignment V4
Previous Message Cédric Villemain 2007-09-04 17:11:17 Re: pg_dump and insert multi-rows option