Re: pg_dump and insert multi-rows option

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Fetter <david(at)fetter(dot)org>, Cédric Villemain <cedric(dot)villemain(at)dalibo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump and insert multi-rows option
Date: 2007-09-04 21:26:59
Message-ID: 200709042126.l84LQxv24675@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> David Fetter <david(at)fetter(dot)org> writes:
> > On Tue, Sep 04, 2007 at 01:22:01PM -0400, Tom Lane wrote:
> >> ... 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.
>
> > I'm pretty sure it does in the current versions of most other DBMSs.
>
> Up to a point, perhaps. Do you want to make assumptions about what
> the maximum acceptable command length will be for other DBMSes?
> It'd be hard enough being sure what to use for Postgres.

Wow, first mention of "Postgres" in the wild. :-) LOL

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chris Browne 2007-09-04 21:41:20 Re: Lazy xid assignment V4
Previous Message Bruce Momjian 2007-09-04 21:24:57 Re: Has anyone tried out the PL/pgSQL debugger?