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

From Daniel Verite
Subject Re: [patch] \g with multiple result sets and \watch with copy queries
Date
Msg-id 321f6823-06c7-4ae9-9cd3-73ff51c22a1d@manitou-mail.org
Whole thread Raw
In response to Re: [patch] \g with multiple result sets and \watch with copy queries  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [patch] \g with multiple result sets and \watch with copy queries  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
    Tom Lane wrote:

> Pushed after making some corrections.

Thanks!

> 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.

Looking at nearby tests, I see that commit d1029bb5a26 brings
interesting additions in test/regress/sql/misc.sql that could be used
as a model to handle output files. psql.sql could write
into PG_ABS_BUILDDIR, then read the files back with \copy I guess,
then output that again to stdout for comparison. I'll see if I can get
that to work.


Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite



pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Assorted fixes related to WAL files (was: Use XLogFromFileName() in pg_resetwal to parse position from WAL file)
Next
From: Matthias van de Meent
Date:
Subject: Re: problems with making relfilenodes 56-bits