Re: [patch] \g with multiple result sets and \watch with copy queries - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [patch] \g with multiple result sets and \watch with copy queries
Date
Msg-id 1816795.1664888924@sss.pgh.pa.us
Whole thread Raw
In response to Re: [patch] \g with multiple result sets and \watch with copy queries  ("Daniel Verite" <daniel@manitou-mail.org>)
Responses Re: [patch] \g with multiple result sets and \watch with copy queries  ("Daniel Verite" <daniel@manitou-mail.org>)
List pgsql-hackers
"Daniel Verite" <daniel@manitou-mail.org> 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 by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: problems with making relfilenodes 56-bits
Next
From: Tom Lane
Date:
Subject: Re: JUMBLE_SIZE macro in two files