pgsql: Original coding of 'returning' regression test inadvertently

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Original coding of 'returning' regression test inadvertently
Date: 2006-08-13 17:58:49
Message-ID: 20060813175849.DFCC79FB20F@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Original coding of 'returning' regression test inadvertently chose a
nonunique join value, leading to plan-choice-dependent results ... and
it seems some platforms will choose a different plan. Tweak the test
so that it has well-defined results. Per report from Olivier Prenant.

Modified Files:
--------------
pgsql/src/test/regress/expected:
returning.out (r1.1 -> r1.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/returning.out.diff?r1=1.1&r2=1.2)
pgsql/src/test/regress/sql:
returning.sql (r1.1 -> r1.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/returning.sql.diff?r1=1.1&r2=1.2)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2006-08-13 19:31:06 pgsql: Extend 'guc' regression test to check manipulations of datestyle
Previous Message Bruce Momjian 2006-08-13 17:31:10 pgsql: Back out plperl OUT hash/array parameter patch, again.