Re: Small issues with CREATE TABLE COMPRESSION - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Small issues with CREATE TABLE COMPRESSION
Date
Msg-id CA+TgmoavG0eN8UdWFwjKEH9LfoYsGzpQxnhPaegnwuAp5d=PHw@mail.gmail.com
Whole thread Raw
In response to Re: Small issues with CREATE TABLE COMPRESSION  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Small issues with CREATE TABLE COMPRESSION
List pgsql-hackers
On Wed, May 5, 2021 at 7:09 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
> So basically, if we have to write this test case in pg_dump then we
> will have to use lz4 which means it will generate different output
> --with-lz4 vs --without-lz4.  With a simple regress test it easy to
> deal with such cases by keeping multiple .out files but I am not sure
> can we do this easily with pg_dump test without adding much
> complexity?

TAP tests have a facility for conditionally skipping tests; see
perldoc Test::More. That's actually superior to what you can do with
pg_regress. We'd need to come up with some logic to determine when to
skip or not, though. Perhaps the easiest method would be to have the
relevant Perl script try to create a table with an lz4 column. If that
works, then perform the LZ4-based tests. If it fails, check the error
message. If it says anything that LZ4 is not supported by this build,
skip those tests. If it says anything else, die.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: RFC: Detailed reorder buffer stats dumps
Next
From: Jakub Wartak
Date:
Subject: RE: Use simplehash.h instead of dynahash in SMgr