Re: [patch] \g with multiple result sets and \watch with copy queries

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Daniel Verite <daniel(at)manitou-mail(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [patch] \g with multiple result sets and \watch with copy queries
Date: 2022-10-10 17:58:02
Message-ID: CADkLM=f--7F=qYEv_znBPKU2Q-+U3ei190t+MZPkZtmJDf7bgg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> This is a bit more complicated than the usual tests, but not
> that much.
> Any opinions on this?

+1

I think that because it is more complicated than usual psql, we may want to
comment on the intention of the tests and some of the less-than-common psql
elements (\set concatenation, resetting \o, etc). If you see value in that
I can amend the patch.

Are there any options on COPY (header, formats) that we think we should
test as well?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2022-10-10 18:10:14 Re: Suppressing useless wakeups in walreceiver
Previous Message Nathan Bossart 2022-10-10 17:51:14 Re: Suppressing useless wakeups in walreceiver