diff options
| author | Tom Lane | 2003-09-19 21:04:20 +0000 |
|---|---|---|
| committer | Tom Lane | 2003-09-19 21:04:20 +0000 |
| commit | a13b01853084b6c6f9c34944bc19b3dd7dc4ceb2 (patch) | |
| tree | 16a4d742afd089eaca684f7e9b86554a044a638d /src/test | |
| parent | fc6b7c550da8ac47df7d34df523428c553e6c9a3 (diff) | |
Disallow foreign-key references from temp tables to permanent tables.
Per recent discussion, this does not work because other backends can't
reliably see tuples in a temp table and so cannot run the RI checks
correctly. Seems better to disallow this case than go back to accessing
temp tables through shared buffers. Also, disallow FK references to
ON COMMIT DELETE ROWS tables. We already caught this problem for normal
TRUNCATE, but the path used by ON COMMIT didn't check.
Diffstat (limited to 'src/test')
| -rw-r--r-- | src/test/regress/expected/truncate.out | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/regress/expected/truncate.out b/src/test/regress/expected/truncate.out index 91ea40b7929..2cd41f83ba0 100644 --- a/src/test/regress/expected/truncate.out +++ b/src/test/regress/expected/truncate.out @@ -42,7 +42,7 @@ SELECT * FROM truncate_a; TRUNCATE truncate_a; ERROR: cannot truncate a table referenced in a foreign key constraint -DETAIL: Table "truncate_b" references this one via foreign key constraint "$1". +DETAIL: Table "truncate_b" references "truncate_a" via foreign key constraint "$1". SELECT * FROM truncate_a; col1 ------ |
