Re: TAP test module - PostgresClient

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: nospam-abuse(at)bloodgate(dot)com, Craig Ringer <craig(at)2ndquadrant(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TAP test module - PostgresClient
Date: 2017-12-30 19:35:27
Message-ID: 4ab7546e-dd48-c985-2b26-e98d58920244@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/30/2017 10:45 AM, Tom Lane wrote:
> Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
>> As for out-dating, if we used DBD::PgPP we'd not be not in great danger
>> there - it doesn't appear to have changed for many years - latest
>> version is dated 2010. If we were to use it we'd have a dependency on
>> DBI, but that in itself doesn't seem a great burden.
> [ blowing the dust off my old red fedora... ] Actually, there's a
> different problem with this proposal: you can bet that DBD::Pg has got a
> build dependency on Postgres. If Postgres starts to depend on DBD::Pg
> then we've created circular-dependency hell for packagers.

The Pure Perl driver has no such dependency, since it doesn't require
libpq. But ...

> I much prefer the other line of thought about doing whatever we need
> to do to make psql workable for the desired type of tests.

... agreed ...

> Or just
> write a bespoke testing tool.
>
>

... that's pretty much where we came in.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2017-12-30 21:04:52 Re: [HACKERS] Re: [HACKERS] generated columns
Previous Message Andres Freund 2017-12-30 16:16:34 Re: pgsql: Add parallel-aware hash joins.