Re: [patch] \g with multiple result sets and \watch with copy queries
От
Tom Lane
Тема
Re: [patch] \g with multiple result sets and \watch with copy queries
Дата
Msg-id
1816795.1664888924@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
[patch] \g with multiple result sets and \watch with copy queries "Daniel Verite" <daniel@manitou-mail.org>
Re: [patch] \g with multiple result sets and \watch with copy queries Tom Lane <tgl@sss.pgh.pa.us>
Re: [patch] \g with multiple result sets and \watch with copy queries Tom Lane <tgl@sss.pgh.pa.us>
Re: [patch] \g with multiple result sets and \watch with copy queries "Daniel Verite" <daniel@manitou-mail.org>
Re: [patch] \g with multiple result sets and \watch with copy queries Tom Lane <tgl@sss.pgh.pa.us>
Re: [patch] \g with multiple result sets and \watch with copy queries "Daniel Verite" <daniel@manitou-mail.org>
Re: [patch] \g with multiple result sets and \watch with copy queries Corey Huinker <corey.huinker@gmail.com>
Re: [patch] \g with multiple result sets and \watch with copy queries "Daniel Verite" <daniel@manitou-mail.org>
Re: [patch] \g with multiple result sets and \watch with copy queries Fabien COELHO <coelho@cri.ensmp.fr>
"Daniel Verite" writes: > Tom Lane wrote: >> Given the time pressure, I did not worry about installing regression >> test coverage for this stuff, but I wonder if we shouldn't add some. > Currently, test/regress/sql/psql.sql doesn't AFAICS write anything > outside of stdout, but \g, \o, \copy need to write to external > files to be tested properly. Yeah, I don't think we can usefully test these in psql.sql, because file-system side effects are bad in that context. But maybe a TAP test could cope? regards, tom lane
В списке pgsql-hackers по дате отправления