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 1hrvtH-0007am-BN for pgsql-hackers@arkaria.postgresql.org; Mon, 29 Jul 2019 02:59:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hrvtF-0006Pu-4m for pgsql-hackers@arkaria.postgresql.org; Mon, 29 Jul 2019 02:59:57 +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 1hrvtE-0006P2-Qv for pgsql-hackers@lists.postgresql.org; Mon, 29 Jul 2019 02:59:56 +0000 Received: from mail-pg1-x530.google.com ([2607:f8b0:4864:20::530]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hrvt9-0000wQ-M5 for pgsql-hackers@lists.postgresql.org; Mon, 29 Jul 2019 02:59:53 +0000 Received: by mail-pg1-x530.google.com with SMTP id t132so27437863pgb.9 for ; Sun, 28 Jul 2019 19:59:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:message-id:to:cc:subject:from:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=mco9pwEgZyj6ZkzNohsr0qjt9ycBkseEvbPnfVXjRnU=; b=uXo4cwuxt66zbxSbJzKkG0tbCv/XhCCHKK68F3bXRxXzQM7SsmDCiPrAln4+MkDIbD e2Gq2uHIODnDY32r2JxOu/5Ejtf460sUEsdbVO3/LbVYGG9D17OjjFYnGzi/iwbSIcvB CSht8u7UnKHGFpx4M7819QqtAt/jZYukFWA3Znp87lEeh8HAHr03TkDMHac7vfhoRVrY 7J9lebuE/8cGfDGXche2LpRD+7EpzXxDiya3zj1LWb4OprNQdyn7VXwmssfQE7Ysik7V 6PbnXidTI2hFVrJUrJ2BmcutfL7oXia+YHgIsUK78f5JsfMQvtqGDYsblg7ige9mRhga 20PA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:message-id:to:cc:subject:from:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=mco9pwEgZyj6ZkzNohsr0qjt9ycBkseEvbPnfVXjRnU=; b=O8JOyzTJKijfCGCU6hzUXHY5zBs4Qhb34au7pPSBQ2F0tSuxfg6V0TmP3eWxebOY4m vCWVaBPrtesgiWw4Spt1D16CNkGy+p65mt3WUobxXtIxH3vaR2PDgQLX1oCJ6ISm6/eV /QehnqF9youDOrUxcnoyxrR761taG6gfz9Y3WKTSVsTrsI07kHVS8ykcyU1MbHrq+a/j 06SA/fA64jkEhDmkxissAc59zHrD0RJI8800xRjh1RVjKpKqroptv05eOnYnQqKsdaZK CWxrZcZbLdBzwnXp+pus97zCqvtbvgkgysjS03fE5oZmbbcZg/cEuwCjG8QqBOeF7iT0 Qtgw== X-Gm-Message-State: APjAAAVsgq3LzPRRGadXLKPcgYZCsC/GJ2UaIBR/kf3Q4WlEb/8TZUyi k/0m3PNIS6y7ec+BwPsskRI= X-Google-Smtp-Source: APXvYqxRCqHQsCHv8Nc22Tp2QRkeKcV/+b/J8+9ROtaPU3WdpClW+vuzv3sFuZB6zH2IESAxuXp0Ag== X-Received: by 2002:aa7:8108:: with SMTP id b8mr34887138pfi.197.1564369188988; Sun, 28 Jul 2019 19:59:48 -0700 (PDT) Received: from localhost (w204177.dynamic.ppp.asahi-net.or.jp. [121.1.204.177]) by smtp.gmail.com with ESMTPSA id y22sm70212045pfo.39.2019.07.28.19.59.46 (version=TLS1 cipher=AES128-SHA bits=128/128); Sun, 28 Jul 2019 19:59:48 -0700 (PDT) Date: Mon, 29 Jul 2019 11:59:38 +0900 (Tokyo Standard Time) Message-Id: <20190729.115938.133494556.horikyota.ntt@gmail.com> To: coelho@cri.ensmp.fr Cc: daniel@manitou-mail.org, peter.eisentraut@2ndquadrant.com, iwata.aya@jp.fujitsu.com, pgsql-hackers@lists.postgresql.org Subject: Re: psql - add SHOW_ALL_RESULTS option From: Kyotaro Horiguchi In-Reply-To: References: <20190726.131704.86173346.horikyota.ntt@gmail.com> User-Agent: Mew version 6.5 on Emacs 22.2 / Mule 5.0 =?iso-2022-jp?B?KBskQjpnGyhCKQ==?= / Meadow-3.01-dev (TSUBO-SUMIRE) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello, Fabien. At Fri, 26 Jul 2019 08:19:47 +0000 (GMT), Fabien COELHO wrote in > > Hello Kyotaro-san, > > >> Attached a v2 for the always-show-all-results variant. Thanks for the > >> debug! > > > > I have some comments on this patch. > > > > I'm +1 for always output all results without having knobs. > > That makes 4 opinions expressed towards this change of behavior, and > none against. > > > Documentation (psql-ref.sgml) has another place that needs the > > same amendment. > > Indeed. > > > Looking the output for -t, -0, -A or something like, we might need > > to introduce result-set separator. > > Yep, possibly. I'm not sure this is material for this patch, though. I'm fine with that. > > # -eH looks broken for me but it would be another issue. > > It seems to work for me. Could you be more precise about how it is > broken? It emits bare command string before html result. It's not caused by this patch. > > Valid setting of FETCH_COUNT disables this feature. I think it is > > unwanted behavior. > > Yes and no: this behavior (bug, really) is pre-existing, FETCH_COUNT > does not work with combined queries: > > sh> /usr/bin/psql > psql (12beta2 ...) > fabien=# \set FETCH_COUNT 2 > fabien=# SELECT 1234 \; SELECT 5432 ; > fabien=# > > same thing with pg 11.4, and probably down to every version of > postgres > since the feature was implemented... > > I think that fixing this should be a separate bug report and > patch. I'll try to look at it. Ah, I didin't notieced that. Thanks for the explanation. > Thanks for the feedback. Attached v3 with further documentation > updates. regards. -- Kyotaro Horiguchi NTT Open Source Software Center