pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Drouvot, Bertrand <bertranddrouvot.pg@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: pgsql: TAP test for logical decoding on standby
Date: Wed, 24 May 2023 13:58:54 +0200
Message-ID: <f0e25007-0852-ee4f-7093-bfd65e5c343c@gmail.com> (raw)
In-Reply-To: <CA+TgmobHGpU2ZkChgKifGDLaf_+mFA7njEpeTjfyNf_msCZYew@mail.gmail.com>
References: <E1pl4qQ-0021HB-Ch@gemulon.postgresql.org>
	<CA+TgmobHGpU2ZkChgKifGDLaf_+mFA7njEpeTjfyNf_msCZYew@mail.gmail.com>

Hi,

On 5/23/23 5:15 PM, Robert Haas wrote:
> On Sat, Apr 8, 2023 at 5:26 AM Andres Freund <andres@anarazel.de> wrote:
>> TAP test for logical decoding on standby
> 
> Small nitpicks:
> 
> 1. The test names generated by check_slots_conflicting_status() start
> with a capital letter, while most other test names start with a
> lower-case letter.
> 

Yeah, not sure that would deserve a fix for its own but if we address 2.
then let's do 1. too.

> 2. The function is called 7 times, 6 with a true argument and 1 with a
> false argument, but the test name only depends on whether the argument
> is true or false, so we get the same test name 6 times. Maybe there's
> not a reasonable way to do better, I'm not sure, but it's not ideal.
> 

I agree that's not ideal (but one could still figure out which one is
failing if any by looking at the perl script).

If we want to "improve" this, what about passing a second argument that
would provide more context in the test name?

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com





view thread (3+ messages)

Message-ID: <f0e25007-0852-ee4f-7093-bfd65e5c343c@gmail.com>
Permalink:  ../f0e25007-0852-ee4f-7093-bfd65e5c343c@gmail.com/
Also on:    postgresql.org/message-id/f0e25007-0852-ee4f-7093-bfd65e5c343c@gmail.com

 · 

reply

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-committers@postgresql.org
  Cc: bertranddrouvot.pg@gmail.com, robertmhaas@gmail.com, andres@anarazel.de, pgsql-hackers@postgresql.org
  Subject: Re: pgsql: TAP test for logical decoding on standby
  In-Reply-To: <f0e25007-0852-ee4f-7093-bfd65e5c343c@gmail.com>

* 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