Re: pg_dump multi VALUES INSERT

From: Surafel Temesgen <surafel3000(at)gmail(dot)com>
To: alvherre(at)2ndquadrant(dot)com
Cc: coelho(at)cri(dot)ensmp(dot)fr, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump multi VALUES INSERT
Date: 2018-11-08 13:02:24
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

On Tue, Nov 6, 2018 at 8:18 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>

> On 2018-Nov-06, Surafel Temesgen wrote:
> > hi,
> >
> > On Sun, Nov 4, 2018 at 1:18 PM Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
> wrote:
> >
> > > Patch does not seem to apply anymore, could you rebase?
> > >
> > The attached patch is a rebased version and work by ‘inserts=100’ as
> > Stephen suggest
> I thought the suggestion was that the number could be any positive
> integer, not hardcoded 100.


> It shouldn't take much more code to handle
> it that way, which makes more sense to me

yes its not much line of code. Attach is a patch that optionally accept the
number of row in a single insert statement and if it is not specified one
row per statement used



Attachment Content-Type Size
multi_values_inserts_dum_v3.patch text/x-patch 9.4 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-11-08 13:19:29 Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query
Previous Message Etsuro Fujita 2018-11-08 12:52:31 Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT