Re: One-shot expanded output in psql using \gx

Stephen Frost <sfrost@snowman.net>

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>

Date: 2017-08-24T20:22:23Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

psql: Fix \gx when FETCH_COUNT is used
- 0cdc3e47bea4 11.0 landed
- 51d0fa8ed93f 10.0 landed
psql: Add \gx command
- b2678efd43f1 10.0 landed

* 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.

Fixed in 0cdc3e4.

Thanks for the report!

Stephen