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 1goSi8-00029C-LI for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Jan 2019 12:41:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1goSi7-0004qu-Bu for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Jan 2019 12:41:51 +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 1goSg8-0004VQ-0e for pgsql-hackers@lists.postgresql.org; Tue, 29 Jan 2019 12:39:48 +0000 Received: from mail-ed1-x541.google.com ([2a00:1450:4864:20::541]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goSg1-0002ym-6z for pgsql-hackers@postgresql.org; Tue, 29 Jan 2019 12:39:47 +0000 Received: by mail-ed1-x541.google.com with SMTP id x30so15882066edx.2 for ; Tue, 29 Jan 2019 04:39:40 -0800 (PST) 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=6NmPlVZ9y5NR4cPmkQvgwAcGCVUun/0WDIjNcs0Jj60=; b=wsz7PQQLGnKxim9JMTeeoy40biV9BbsIgmtTcDIbpf1zNX0x5J2kUOdUmHhKq8Mo8w 3ipb6c422tlAK6dlLUNXCha0AYMHwXV5eXqcmveLawrMa1X09AwEheYUNioGWepFKbnS ey1LMDdLfbuCdseqZ2ZQ6zdotblgEAyaC/UzVhUuB8A/ZVPBnAhgVa8DgIjkBV41M+pV yfjbr/WNmSEePwhI/wVxFkORT8+D+KTMrM9pMUuFGsvKFYB2boRhE0LlCanuumRAjoPU YRuNZP859LNMcNrlwELC3AKi6kyXX+Zi9bc+gDXwOa+PVONz0UagEa4rbSGWKGnthT2w Dl3g== 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=6NmPlVZ9y5NR4cPmkQvgwAcGCVUun/0WDIjNcs0Jj60=; b=tkVGYV9v+2Tka2kuTEfI2ZeoM1O5WsrRGhOIsU/HnE5Q738CqVx2mBBGaHdFyzmqIE UzZ9jvTZvYs0m2kE6z9vzOHRsnK3f1mVoU0gh52bVhQ5NG12c358vUKYZuzJLfKOXYa9 wvDrDf/CSTJRqO0C6kMg5HHqWTeWdMKt6uWO/pqA3FQPB/msSe9w8o1C2+2SgFebXxVS LZQc60ZZEwuONf4YlWQN9DBCnQXuiXyp8v4KU0hz2mq6dHeWx+WyzW/Xx4xxcY+PVKRv 4/+BYsgWMkquWqORB5I1sy70TxwbdobLlAKIvtZIQsxL41IcLyPanH6RaonvVoXqfao6 J58w== X-Gm-Message-State: AJcUukf4Gmi0xNi9Dxe6qcr0+0OIH1N66DK3WdEAWbWGXxqpHtOP0f9r ok9EjqRiCXpWycqdry/eXU2Obw== X-Google-Smtp-Source: ALg8bN5qcc14+U3bObwWTNq4GkbScUsbtz/F5v+OSg4BOmiST9oabXvw5wRuKKL41xWtoTr+AEvnJw== X-Received: by 2002:a17:906:2316:: with SMTP id l22mr5303437eja.91.1548765579363; Tue, 29 Jan 2019 04:39:39 -0800 (PST) Received: from alvin.alvh.no-ip.org ([212.76.254.98]) by smtp.gmail.com with ESMTPSA id s3sm14370949edm.31.2019.01.29.04.39.37 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 29 Jan 2019 04:39:38 -0800 (PST) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id AB5C9A3F; Tue, 29 Jan 2019 06:24:33 -0300 (-03) Date: Tue, 29 Jan 2019 06:24:33 -0300 From: Alvaro Herrera To: David Rowley Cc: Surafel Temesgen , Fabien COELHO , Dmitry Dolgov <9erthalion6@gmail.com>, PostgreSQL-development Subject: Re: pg_dump multi VALUES INSERT Message-ID: <201901290924.xw464ogexx74@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180716-1013-2c1e88 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Jan-23, David Rowley wrote: > On Wed, 23 Jan 2019 at 04:08, Alvaro Herrera wrote: > > Is it possible to avoid the special case for 0 columns by using the > > UNION ALL syntax I showed? > > It would be possible, but my thoughts are that we're moving away from > the SQL standard by doing so. Ah, that's a good point that I missed -- I agree with your reasoning. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services