MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 08 Apr 2015 14:31:38 +0200
From: Jan Lentfer <Jan.Lentfer@web.de>
To: <pgsql-admin@postgresql.org>
Subject: Re: pgdump with batch insert
In-Reply-To: 
 <CALXoLqxb7FxeLZHK91GotuQ0-4=zGCK6V4Pw2HnTQv_OiBwmug@mail.gmail.com>
References: 
 <CALXoLqxb7FxeLZHK91GotuQ0-4=zGCK6V4Pw2HnTQv_OiBwmug@mail.gmail.com>
Message-ID: <3341486aeec8f791e6bb29e637319273@imap.lan.net>
User-Agent: Roundcube Webmail/0.7.2
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Am 2015-04-08 14:02, schrieb Ankur Kaushik:
> Is there possibility in pgdump to get insert statement in batch 
> insert
> into tablename value(),(),(),;
>
> as well as We can use replace keyword or insert ignore .

Have you read the documentation for pg_dump?

http://www.postgresql.org/docs/9.3/static/app-pgdump.html

--inserts

     Dump data as INSERT commands (rather than COPY). This will make 
restoration very slow; it is mainly useful for making dumps that can be 
loaded into non-PostgreSQL databases. However, since this option 
generates a separate command for each row, an error in reloading a row 
causes only that row to be lost rather than the entire table contents. 
Note that the restore might fail altogether if you have rearranged 
column order. The --column-inserts option is safe against column order 
changes, though even slower.


Regards

Jan


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin