Re: Testing of MVCC

From: Tino Wildenhain <tino(at)wildenhain(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 07:22:34
Message-ID: 4301943A.6090503@wildenhain.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Tom Lane schrieb:
> Greg Stark <gsstark(at)mit(dot)edu> writes:
>
>>So why bother with driving multiple invocations of psql under
>>Expect. Just use DBD::Pg to open as many connections as you want and
>>issue whatever queries you want.
>
>
> The bit that I think is missing in DBI is "issue a command and don't
> wait for the result just yet". Without that, you cannot for instance
> stack up several waiters for the same lock, as you might wish to do to
> verify that they get released in the correct order once the original
> lock holder goes away. Or stack up some conflicting waiters and check
> to see if deadlock is detected when it should be ... or contrariwise,
> not signalled when it should not be. There's lots of stuff you can
> do that isn't exactly probing for race conditions, yet would be awfully
> nice to check for in a routine test suite.
>
> 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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ulrich Wisser 2005-08-16 07:29:02 Re: vacuum error "left link changed unexpectedly"
Previous Message Pit Müller 2005-08-16 07:02:35 Re: libpy and ENABLE_THREAD_SAFETY=1

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2005-08-16 07:39:14 Re: ARRAY(subquery) volatility
Previous Message Michael Fuhr 2005-08-16 06:04:14 ARRAY(subquery) volatility