Re: pg_dump and insert multi-rows option - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pg_dump and insert multi-rows option
Date
Msg-id 46DDB832.4000500@dunslane.net
Whole thread Raw
In response to Re: pg_dump and insert multi-rows option  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump and insert multi-rows option
List pgsql-hackers

Tom Lane wrote:
> David Fetter <david@fetter.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.
>
>     
>   

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


pgsql-hackers by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Has anyone tried out the PL/pgSQL debugger?
Next
From: "Brendan Jurd"
Date:
Subject: Re: Per-function GUC settings: trickier than it looked