| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [patch] \g with multiple result sets and \watch with copy queries |
| Date: | 2022-10-07 13:18:54 |
| Message-ID: | 38680033-f9b7-4c7d-a729-8487e8e51308@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> > 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?
I've came up with the attached using psql.sql only, at least for
\g and \o writing to files.
This is a bit more complicated than the usual tests, but not
that much.
Any opinions on this?
Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite
| Attachment | Content-Type | Size |
|---|---|---|
| tests-psql-g-o-file.patch | text/plain | 5.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2022-10-07 13:55:39 | Re: ps command does not show walsender's connected db |
| Previous Message | Denis Laxalde | 2022-10-07 13:08:05 | [PATCH] Reset single-row processing mode at end of pipeline commands queue |