From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: TAP output format in pg_regress |
Date: | 2022-06-29 19:50:45 |
Message-ID: | 489D2B5A-B26F-4918-BC07-B426329169E3@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Attached is a new version of this patch, which completes the TAP output format
option such that all codepaths emitting output are TAP compliant. The verbose
option is fixed to to not output extraneous newlines which the previous PoC
did. The output it made to conform to the original TAP spec since v13/14 TAP
parsers seem less common than those that can handle the original spec. Support
for the new format additions should be quite simple to add should we want that.
Running pg_regress --verbose should give the current format output.
I did end up combining TAP and --verbose into a single patch, as the TAP format
sort of depends on the verbose flag as TAP has no verbose mode. I can split it
into two separate should a reviewer prefer that.
--
Daniel Gustafsson https://vmware.com/
Attachment | Content-Type | Size |
---|---|---|
v5-0001-pg_regress-TAP-output-format.patch | application/octet-stream | 38.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Dudoladov | 2022-06-29 20:42:44 | Re: Stats collector's idx_blks_hit value is highly misleading in practice |
Previous Message | Erik Rijkers | 2022-06-29 19:07:52 | Re: PostgreSQL 15 beta 2 release announcement draft |