Re: pg_dump and insert multi-rows option

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
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 19:55:30
Message-ID: 46DDB832.4000500@dunslane.net
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.
>
>
>

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Brendan Jurd 2007-09-04 20:11:57 Re: Per-function GUC settings: trickier than it looked
Previous Message Richard Huxton 2007-09-04 19:45:42 Re: Has anyone tried out the PL/pgSQL debugger?