From 15386281a62071f322155b74cb32c2fea92e8350 Mon Sep 17 00:00:00 2001
From: Heikki Linnakangas
Date: Mon, 3 Jun 2013 17:22:31 +0300
Subject: Put back allow_system_table_mods check in heap_create().

This reverts commit a475c6036752c26dca538632b68fd2cc592976b7.

Erik Rijkers reported back in January 2013 that after the patch, if you do
"pg_dump -t myschema.mytable" to dump a single table, and restore that in
a database where myschema does not exist, the table is silently created in
pg_catalog instead. That is because pg_dump uses
"SET search_path=myschema, pg_catalog" to set schema the table is created
in. While allow_system_table_mods is not a very elegant solution to this,
we can't leave it as it is, so for now, revert it back to the way it was
previously.
---
 src/backend/bootstrap/bootparse.y | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'src/backend/bootstrap')

diff --git a/src/backend/bootstrap/bootparse.y b/src/backend/bootstrap/bootparse.y
index d40fd6827c0..cee72c186b0 100644
--- a/src/backend/bootstrap/bootparse.y
+++ b/src/backend/bootstrap/bootparse.y
@@ -222,7 +222,8 @@ Boot_CreateStmt:
 												   RELKIND_RELATION,
 												   RELPERSISTENCE_PERMANENT,
 												   shared_relation,
-												   mapped_relation);
+												   mapped_relation,
+												   true);
 						elog(DEBUG4, "bootstrap relation created");
 					}
 					else
-- 
cgit v1.2.3