Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hbnMH-0005pJ-3c for pgsql-hackers@arkaria.postgresql.org; Fri, 14 Jun 2019 14:39:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hbnMF-0005jS-95 for pgsql-hackers@arkaria.postgresql.org; Fri, 14 Jun 2019 14:39:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hbnME-0005gv-Rj for pgsql-hackers@lists.postgresql.org; Fri, 14 Jun 2019 14:39:11 +0000 Received: from mail-qt1-x842.google.com ([2607:f8b0:4864:20::842]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hbnM6-0001zA-AG for pgsql-hackers@postgresql.org; Fri, 14 Jun 2019 14:39:09 +0000 Received: by mail-qt1-x842.google.com with SMTP id x2so2743399qtr.0 for ; Fri, 14 Jun 2019 07:39:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=bUrX8g6cNY36HImagEDSnguPVBD9xjKf4U5aHqwxEe4=; b=yRukoRjS7WCRVzVtqVqQx1Z1+2hR55I6q43j1uBScZxW4k1ZQZpNl37F29MZQbMRv5 VzDq022S6qTvBSwy3kLrt1fXbXR28XKJ4xYfbQ1GMyGE9abu+BsramUe82hg0Y8BQkCW iKA8ahYdY2D6CteR1G5J+ybIcmuAD1qFG7PhPmaSCoGJ4jh8tpWq5cTl9lmEVv8jVJCe nzxLXxqS/CKJHjpflrHP3qQ+FeqO+v428S3Mgi0cKqVipQM5nXQqzPILho54n7m9HmU/ uzHIReU1pGSf6F9tXZAF/ec83fCIy1DQIioyfZwup89KgSsCYSanJOR8rn3mWzeX60SB GYIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=bUrX8g6cNY36HImagEDSnguPVBD9xjKf4U5aHqwxEe4=; b=Wum/9h05ePXGYYZQNv/ZyVnrbB5xXPVkGmcVJtUtIhF8KDYXCio9uo1wTjTluXvj4m iRzfSUX8+Lui1HOrNGJgeUVnb80NFrXLwft2eOo3INp6zh5jecA2YT9IwvIbQrFsGWnZ jEFHBpvgocMUFmlmhiaaX5kAzBhL3JeFEtAJUrKVOqlEYhgHDhic+w3qCmVOz0L7lT5D z1gOJLFDHFDNtZiVw9bpmjGcxcFvWYDEnO3pzgCIzseKfGdzDwUegBSBdAdfTH8OIZ4U Oxrs2UCnyU9i+ODLXHxIWcFrfGQVoA6gYpKYd/b+txVhOJ+ruxinEyKctPMqUb/0pmxQ Nbsw== X-Gm-Message-State: APjAAAWE8OOt/yFQYRPZSAjPaOAs9LPk34EcSwvIsSTt2rGJb+OWjMbU b8D4S/flWI/tebcMFyaQTowtAQ== X-Google-Smtp-Source: APXvYqylAK+ezRFcAgXK9wsQrCuALaOq4Yp+rvkjTk23RCPaVLP5thnHB1nip6cCwFm0ZjHLNjGGKA== X-Received: by 2002:a0c:d003:: with SMTP id u3mr8799541qvg.112.1560523139782; Fri, 14 Jun 2019 07:38:59 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([179.56.48.227]) by smtp.gmail.com with ESMTPSA id u125sm1488689qkd.5.2019.06.14.07.38.58 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 14 Jun 2019 07:38:59 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 2E276120988; Fri, 14 Jun 2019 10:38:55 -0400 (-04) Date: Fri, 14 Jun 2019 10:38:55 -0400 From: Alvaro Herrera To: Peter Eisentraut Cc: David Rowley , Fabien COELHO , Surafel Temesgen , Dmitry Dolgov <9erthalion6@gmail.com>, PostgreSQL-development Subject: Re: pg_dump multi VALUES INSERT Message-ID: <20190614143855.GA3267@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <45f50c59-ddbb-8cf2-eedb-81003f603528@2ndquadrant.com> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Jun-14, Peter Eisentraut wrote: > Shouldn't the --rows-per-insert option also be available via pg_dumpall? > All the other options for switching between COPY and INSERT are > settable in pg_dumpall. Uh, yeah, absolutely. Surafel, are you in a position to provide a patch for that quickly? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services