pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Postgres perl module namespace
Date: Tue, 10 Aug 2021 10:40:43 -0400
Message-ID: <3784121.1628606443@sss.pgh.pa.us> (raw)
In-Reply-To: <1290c0d8-f619-0fa2-7c2f-8077ad967bbc@dunslane.net>
References: <aede93a4-7d92-ef26-398f-5094944c2504@dunslane.net>
	<3796296.1621545509@sss.pgh.pa.us>
	<1290c0d8-f619-0fa2-7c2f-8077ad967bbc@dunslane.net>

Andrew Dunstan <andrew@dunslane.net> writes:
> I will undertake to do the work, once we get the bike-shedding part done.

> I'll kick that off by suggesting we move all of these to the namespace
> PgTest, and rename TestLib to Utils, so instead of
>     use TestLib;
>     use PostgresNode;
> you would say
>     use PgTest::Utils;
>     use PgTest::PostgresNode;

Using both "Pg" and "Postgres" seems a bit inconsistent.
Maybe "PgTest::PgNode"?

More generally, I've never thought that "Node" was a great name
here; it's a very vague term.  While we're renaming, maybe we
could change it to "PgTest::PgCluster" or the like?

			regards, tom lane





view thread (63+ messages)  latest in thread

Message-ID: <3784121.1628606443@sss.pgh.pa.us>
Permalink:  ../3784121.1628606443@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3784121.1628606443@sss.pgh.pa.us

 · 

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-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, pgsql-hackers@lists.postgresql.org
  Subject: Re: Postgres perl module namespace
  In-Reply-To: <3784121.1628606443@sss.pgh.pa.us>

* 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