Date: Wed, 23 Aug 2017 20:45:58 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Noah Misch <noah@leadboat.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
	Christoph Berg <christoph.berg@credativ.de>,
	Daniel Verite <daniel@manitou-mail.org>,
	David Fetter <david@fetter.org>,
	Tobias Bussmann <t.bussmann@gmx.net>
Subject: Re: One-shot expanded output in psql using \gx
Message-ID: <20170824004558.GV4628@tamriel.snowman.net>
References: <20170306124233.c64cylgyot7ipeix@msg.credativ.de>
 <2d2f2c0f-6ba8-476d-bc98-49b098fd2c66@manitou-mail.org>
 <20170307131541.GF9812@tamriel.snowman.net>
 <CB7A53AA-5645-4BDD-AB07-4D22CD9D8FF1@gmx.net>
 <20170817022441.GA3963697@rfd.leadboat.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="Twje0N0eLdQmUbrK"
Content-Disposition: inline
In-Reply-To: <20170817022441.GA3963697@rfd.leadboat.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


--Twje0N0eLdQmUbrK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Noah Misch (noah@leadboat.com) wrote:
> On Tue, Aug 15, 2017 at 10:24:34PM +0200, Tobias Bussmann wrote:
> > I've tested the new \gx against 10beta and current git HEAD. Actually o=
ne of my favourite features of PostgreSQL 10! However in my environment it =
was behaving strangely. After some debugging I found that \gx does not work=
 if you have \set FETCH_COUNT n before. Please find attached a patch that f=
ixes this incl. new regression test.
>=20
> [Action required within three days.  This is a generic notification.]
>=20
> The above-described topic is currently a PostgreSQL 10 open item.  Stephe=
n,
> since you committed the patch believed to have created it, you own this o=
pen
> item.  If some other commit is more relevant or if this does not belong a=
s a
> v10 open item, please let us know.  Otherwise, please observe the policy =
on
> open item ownership[1] and send a status update within three calendar day=
s of
> this message.  Include a date for your subsequent status update.  Testers=
 may
> discover new open items at any time, and I want to plan to get them all f=
ixed
> well in advance of shipping v10.  Consequently, I will appreciate your ef=
forts
> toward speedy resolution.  Thanks.

Just to preempt the coming nagging email, yes, I'm aware I didn't get to
finish this today (though at least today, unlike yesterday, I looked at
it and started to play with it..  I blame the celestial bodies that
caused an impressive traffic jam on Monday night causing me to lose
basically all of Tuesday too..).

I'll provide an update tomorrow.

Thanks!

Stephen

--Twje0N0eLdQmUbrK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJZniHGAAoJEO1sijiDR2RVma8P/iMFZF8HkfZQcBu2lYLRE+wb
6e5oaNwCfIXZs3+iMd9UNBfUbwPxZt4tbtuXzf9SlGgstYvX76OozzE8WfG24NHv
xjY343Dis920UnQc6F7qQkwQw98vdOHR83whg7U9nni5gIAUlmE/XqzT2EynSX02
/9cq1JvmQc7eE+Pw4FSy47ocEypFEbcfSoRu5olj7T7H3a6wf0PlqynyTKXEtwLe
IVPV4MDJ0BDR6FWb1dNKDqRm32duA8OMaWJ541Ov0XNwmLRikDvYC0OVd7uB/Cw1
y4VNSUIvQtPTnpPsWtmjNbYvBFfymdMa6enUSYpddD9L2xKKz3AIM3K7V5QWGX10
jX3+cOpZnQU+GY3e4pHjFgskI3OoBZuygFS+ZtsOd80XxMQcjueZyStvWf81EwIV
yshuuseyTq5smvI1e8oypYLkc9+hIUvpZDfi+QrUz3EmAbNvS9gtDIjMlf8ygjVo
B2uZgsA2CdtAC2Q1nLb8JgpID4XBKO9KwdOUCa7VImEYT8rFRomYnIQ6yRWCXww9
beQEY07/zwx6u79InqjV6BCYGIyTBklNSKfgriyrNXIcoU8eNSEULrzEqnFOzKxT
YEypj0Yw6CQIR4rFrWJdytS3Smy5lsIMM/WkziE/2YgVxLzT6raSZ8XLtIPPEswu
T6WrPsT/yxvIsTeo4j66
=9Ymk
-----END PGP SIGNATURE-----

--Twje0N0eLdQmUbrK--