From: Stephen Frost <sfrost@snowman.net>
To: Noah Misch <noah@leadboat.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Christoph Berg <christoph.berg@credativ.de>
Cc: Daniel Verite <daniel@manitou-mail.org>
Cc: David Fetter <david@fetter.org>
Cc: Tobias Bussmann <t.bussmann@gmx.net>
Subject: Re: One-shot expanded output in psql using \gx
Date: Wed, 23 Aug 2017 20:45:58 -0400
Message-ID: <20170824004558.GV4628@tamriel.snowman.net> (raw)
In-Reply-To: <20170817022441.GA3963697@rfd.leadboat.com>
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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
* 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 one 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 fixes this incl. new regression test.
>
> [Action required within three days. This is a generic notification.]
>
> The above-described topic is currently a PostgreSQL 10 open item. Stephen,
> since you committed the patch believed to have created it, you own this open
> item. If some other commit is more relevant or if this does not belong as 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 days 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 fixed
> well in advance of shipping v10. Consequently, I will appreciate your efforts
> 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
Attachments:
signature.asc (application/pgp-signature, 818B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: sfrost@snowman.net, noah@leadboat.com, christoph.berg@credativ.de, daniel@manitou-mail.org, david@fetter.org, t.bussmann@gmx.net
Subject: Re: One-shot expanded output in psql using \gx
In-Reply-To: <20170824004558.GV4628@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox