Re: Testing of MVCC

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tino Wildenhain <tino(at)wildenhain(dot)de>, Greg Stark <gsstark(at)mit(dot)edu>, Matt Miller <mattm(at)epx(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Testing of MVCC
Date: 2005-08-16 15:18:05
Message-ID: 1554.1124205485@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> Another line of thought is to write a fresh implementation of the wire
>> protocol all in Perl, so as not to depend on DBI or much of anything
>> except Perl's TCP support (which I hope is reasonably well standardized
>> ;-)). If you wanted to do any testing at the protocol level ---
>> handling of bad messages, say --- you'd pretty much need this anyway
>> because no driver is going to let you get at things at such a low level.
>> But it'd raise the cost of getting started quite a bit.

> Maybe pulling some code from this would give us a leg up rather than
> having to start from scratch: http://search.cpan.org/~arc/DBD-PgPP-0.05/

Another thought on this point: I think most of the pain is associated
with handling the startup authentication negotiation (at least if you
want to support all the auth method options). Once you've got a live
connection the protocol's not all that complicated. So one way to
leverage some code would be to use DBD or another existing driver to
handle the startup phase, and then just hack it to turn over the bare
socket to the test code.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Oluwatope Akinniyi 2005-08-16 15:54:15 Re: ~/pgpass
Previous Message Tom Lane 2005-08-16 15:12:11 Re: Testing of MVCC

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2005-08-16 15:53:22 Re: pl/Ruby, deprecating plPython and Core
Previous Message Tom Lane 2005-08-16 15:12:11 Re: Testing of MVCC