From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Nikolay Shaplov <dhyan@nataraj.su>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Cc: Andres Freund <andres@anarazel.de>
Subject: Re: [PATCH] Tests for reloptions
Date: Thu, 19 Oct 2017 14:20:52 +0200
Message-ID: <20171019122052.f3cychhfktrfwqdk@alvherre.pgsql> (raw)
In-Reply-To: <1933219.021c0Pr2Ov@x200m>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Nikolay Shaplov wrote:
> В письме от 3 октября 2017 11:48:43 пользователь Michael Paquier написал:
> I've been thinking a lot, and rereading the patch. When I reread it I've been
> thinking that I would like to add more tests to it now... ;-)
>
> If the only purpose of tests is to get better coverage, then I would agree
> with you. But I've been thinking that tests also should check that everything
> behaves as expected (or as written in documentation).
>
> I would say that options names is a of part of SQL dialect that postgres uses,
> kind of part of the syntax. It is good to be sure that they still supported.
> So I would add a test for every option heap supports.
Yeah, it would perhaps be good idea to ensure we don't break things that
are documented to work. If the tests don't take too long, I'm not
opposed to testing every single option. As you say, code coverage is
important but it's not the only goal.
I'm hesitant to hardcode things like the number of bits in bloom, as you
had in the original. If I understand correctly, that number could
change with compile options (different blocksize?), so I removed that
part. I also fixed a few spelling errors.
And pushed. Let's see what the buildfarm says about this.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, dhyan@nataraj.su, michael.paquier@gmail.com, andres@anarazel.de
Subject: Re: [PATCH] Tests for reloptions
In-Reply-To: <20171019122052.f3cychhfktrfwqdk@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox