Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YkwgY-0003Oq-TP for pgsql-admin@arkaria.postgresql.org; Wed, 22 Apr 2015 15:35:35 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YkwgX-0005tD-WF for pgsql-admin@arkaria.postgresql.org; Wed, 22 Apr 2015 15:35:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YkwgW-0005rK-PD for pgsql-admin@postgresql.org; Wed, 22 Apr 2015 15:35:32 +0000 Received: from mail-wi0-x231.google.com ([2a00:1450:400c:c05::231]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YkwgT-0005Ku-6W for pgsql-admin@postgresql.org; Wed, 22 Apr 2015 15:35:31 +0000 Received: by widdi4 with SMTP id di4so182690765wid.0 for ; Wed, 22 Apr 2015 08:35:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:reply-to:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; bh=xuwWzIFM91P9Rt4mPvhspaSfaH0LMOVX/kStyuiKEEI=; b=BvmR/1ClPG2/v1qIyuvQnafurrK29dg2DuETcRgIGgjwhW/Y/jFcwwWLchmHaEsvrz kKLEKVZ1mnFePuidsyoFlirVx0PMGIGU69fCc1AYKygM1eAteuOjatshuQQrFES3incW 9wCxKGT9GMIBvcPNL0Qg/WHoIgWWL/NUI36xD0fCf7aL6JnhWyYgbwZbYQAr9KJO9zc5 i1mgs+Xc6BcGBEQHKbQipcurt0E7rkFKefTpgYGoG1w0GI4SqrYWoVkm3STEgA1ISzSg TAbKi1ujrKyXFY+6mjkhLeFO1W8hm/s6/7Q8jceyUKFukYKRjHQPjSEWigl9jX7uNMU8 dE5g== X-Received: by 10.180.109.136 with SMTP id hs8mr6863422wib.73.1429716928019; Wed, 22 Apr 2015 08:35:28 -0700 (PDT) Received: from enterprisedb01 (213.37.154.13.static.user.ono.com. [213.37.154.13]) by mx.google.com with ESMTPSA id ha4sm24911407wib.0.2015.04.22.08.35.26 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Apr 2015 08:35:27 -0700 (PDT) Message-ID: <1429716924.19045.19.camel@gmail.com> Subject: Re: pgdump with batch insert From: jaime soler Reply-To: jaime.soler@gmail.com To: Ankur Kaushik Cc: pgsql-admin@postgresql.org Date: Wed, 22 Apr 2015 17:35:24 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.10-0ubuntu1~14.10.1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org El mié, 08-04-2015 a las 17:32 +0530, Ankur Kaushik escribió: > Hi , > > > > > Is there possibility in pgdump to get insert statement in batch insert > into tablename value(),(),(),; No, pg_dump doesn't generate insert statements of multiple values, just one value per insert with --inserts > > > as well as We can use replace keyword or insert ignore . -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin