Skip site navigation (1) Skip section navigation (2)

Re: Visibility regression test

From: Rod Taylor <rbt(at)zort(dot)ca>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, John Gray <jgray(at)azuli(dot)co(dot)uk>,Manfred Koizar <mkoi-pg(at)aon(dot)at>,PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Visibility regression test
Date: 2002-08-29 17:13:46
Message-ID: 1030641228.4458.5.camel@jester (view raw or flat)
Thread:
Lists: pgsql-patches
> You could actually serialize all of the commands from one backend, 
> against multiple backends, using dblink.

That doesn't help, it changes the connection method but the problem is
still there.

Backend A locks row
Backends B and C are waiting on row
Backend A releases row

The problem is we cannot determine the order that B and C will wake up
in, which makes doing a diff against a standard case difficult.


We don't actually want to serialize the commands as that changes the
test.


In response to

Responses

pgsql-patches by date

Next:From: D'Arcy J.M. CainDate: 2002-08-29 17:17:35
Subject: Re: Proposed GUC Variable
Previous:From: Tomoyuki NiijimaDate: 2002-08-29 17:06:56
Subject: failed to build libpq.so on AIX 4 and 5/I have a solution

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group