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

Re: Visibility regression test

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rod Taylor <rbt(at)zort(dot)ca>
Cc: Joe Conway <mail(at)joeconway(dot)com>, 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:22:43
Message-ID: 19669.1030641763@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Rod Taylor <rbt(at)zort(dot)ca> writes:
> 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.

Exactly.

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

Good point.  Maybe what we need is not so much emphasis on getting an
exactly predetermined output, as a way of understanding the allowed
variations in output order and making the tool able to complain just
when unexpected variation occurs.  In other words, something smarter
than diff to check the results with.

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: Tom LaneDate: 2002-08-29 17:27:36
Subject: Re: Visibility regression test
Previous:From: Manfred KoizarDate: 2002-08-29 17:21:48
Subject: Re: Visibility regression test

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