aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gin/gininsert.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2012-06-14 09:58:53 -0400
committerRobert Haas <rhaas@postgresql.org>2012-06-14 09:58:53 -0400
commita475c6036752c26dca538632b68fd2cc592976b7 (patch)
treed6396fceca29a112638d621ea71eed61282ada00 /src/backend/access/gin/gininsert.c
parentd2c86a1ccd17145eeed2377ff7930e2ccbf5869e (diff)
downloadpostgresql-a475c6036752c26dca538632b68fd2cc592976b7.tar.gz
postgresql-a475c6036752c26dca538632b68fd2cc592976b7.zip
Remove misplaced sanity check from heap_create().
Even when allow_system_table_mods is not set, we allow creation of any type of SQL object in pg_catalog, except for relations. And you can get relations into pg_catalog, too, by initially creating them in some other schema and then moving them with ALTER .. SET SCHEMA. So this restriction, which prevents relations (only) from being created in pg_catalog directly, is fairly pointless. If we need a safety mechanism for this, it should be placed further upstream, so that it affects all SQL objects uniformly, and picks up both CREATE and SET SCHEMA. For now, just rip it out, per discussion with Tom Lane.
Diffstat (limited to 'src/backend/access/gin/gininsert.c')
0 files changed, 0 insertions, 0 deletions