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

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Christoph Berg <christoph(dot)berg(at)credativ(dot)de>, Daniel Verite <daniel(at)manitou-mail(dot)org>, David Fetter <david(at)fetter(dot)org>, Tobias Bussmann <t(dot)bussmann(at)gmx(dot)net>
Subject: Re: One-shot expanded output in psql using \gx
Date: 2017-08-19 17:23:45
Message-ID: 20170819172345.GL4628@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Noah, all,

* Noah Misch (noah(at)leadboat(dot)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.]

I'll address this on Tuesday, 8/22.

Thanks!

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-08-19 17:40:42 Re: Segmentation Fault during pg_restore using '--use-list' and '--jobs'
Previous Message Tom Lane 2017-08-19 17:03:37 Re: [RFC] What would be difficult to make data models pluggable for making PostgreSQL a multi-model database?