This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---------------------------------------------------------------------------
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
> > David Fetter <[EMAIL PROTECTED]> 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.
> >
> >
> >
>
> If we were going to allow it then I think we'd also need a param to
> specify either a max number of rows or a max statement size. IIRC, in
> MySQL at least, one of these is tunable for input.
>
> cheers
>
> andrew
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
--
Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
