Re: Testing of MVCC

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

Tino Wildenhain <tino(at)wildenhain(dot)de> writes:
> Tom Lane schrieb:
>> The bit that I think is missing in DBI is "issue a command and don't
>> wait for the result just yet". ...
>> I might be wrong though, not being exactly a DBI guru ... can this
>> sort of thing be done?
>>
> I wonder if you dont have a wrapper around libpq you can use like that?

Sure, it wouldn't take much to create a minimal C+libpq program that
would do the basics. But the history of testing tools teaches that
you soon find yourself wanting a whole lot more functionality, like
conditional tests, looping, etc, in the test-driver mechanism.
That's the wheel that I don't want to re-invent. And it's a big part
of the reason why stuff like Expect and the Perl Test modules have
become so popular: you have a full scripting language right there at
your command.

Maybe the right answer is just to hack up Pg.pm or DBD::Pg to provide
the needed asynchronous-command-submission facility, and go forward
from there using the Perl Test framework.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message WELTY, RICHARD 2005-08-16 13:39:00 Re: Postgresql Books: Which one ?
Previous Message Surabhi Ahuja 2005-08-16 12:16:04 regarding isolation amongst threads

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2005-08-16 13:42:04 Re: pl/Ruby, deprecating plPython and Core
Previous Message Dave Cramer 2005-08-16 12:08:07 Re: pl/Ruby, deprecating plPython and Core