mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add an ORDER BY to nail down the expected row order from a query that's

Browse Source 
been shown to be sensitive to concurrent autovacuum.  Per Alvaro.
This commit is contained in:
Tom Lane 2007-09-03 01:28:40 +00:00
parent a4df52f95f
commit 6f4a5462b4
2 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/test/regress/expected/cluster.out
View File

@ -249,11 +249,12 @@ SELECT a,b,c,substring(d for 30), length(d) from clstr_tst;
INSERT INTO clstr_tst (b, c) VALUES (1111, 'this should fail'); INSERT INTO clstr_tst (b, c) VALUES (1111, 'this should fail');
ERROR: insert or update on table "clstr_tst" violates foreign key constraint "clstr_tst_con" ERROR: insert or update on table "clstr_tst" violates foreign key constraint "clstr_tst_con"
DETAIL: Key (b)=(1111) is not present in table "clstr_tst_s". DETAIL: Key (b)=(1111) is not present in table "clstr_tst_s".
SELECT conname FROM pg_constraint WHERE conrelid = 'clstr_tst'::regclass; SELECT conname FROM pg_constraint WHERE conrelid = 'clstr_tst'::regclass
ORDER BY 1;
conname conname
---------------- ----------------
clstr_tst_pkey
clstr_tst_con clstr_tst_con
clstr_tst_pkey
(2 rows) (2 rows)
SELECT relname, relkind, SELECT relname, relkind,

3
src/test/regress/sql/cluster.sql
View File

@ -73,7 +73,8 @@ SELECT a,b,c,substring(d for 30), length(d) from clstr_tst;
-- Verify that foreign key link still works -- Verify that foreign key link still works
INSERT INTO clstr_tst (b, c) VALUES (1111, 'this should fail'); INSERT INTO clstr_tst (b, c) VALUES (1111, 'this should fail');
SELECT conname FROM pg_constraint WHERE conrelid = 'clstr_tst'::regclass; SELECT conname FROM pg_constraint WHERE conrelid = 'clstr_tst'::regclass
ORDER BY 1;
SELECT relname, relkind, SELECT relname, relkind,