Re: psql - add SHOW_ALL_RESULTS option

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "Iwata, Aya" <iwata(dot)aya(at)jp(dot)fujitsu(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: psql - add SHOW_ALL_RESULTS option
Date: 2020-07-20 05:48:42
Message-ID: alpine.DEB.2.22.394.2007200747040.2368970@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

>> In the meantime, here is a v9 which also fixes the behavior when using
>> \watch, so that now one can issue several \;-separated queries and have
>> their progress shown. I just needed that a few days ago and was
>> disappointed but unsurprised that it did not work.
> This seems to break the test.

Yes, indeed. I'm planning to investigate, hopefully this week.


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2020-07-20 06:31:36 Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions
Previous Message 2020-07-20 05:42:59 Re: pg_resetwal --next-transaction-id may cause database failed to restart.