aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeSetOp.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-03-21 14:09:39 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2012-03-21 14:09:39 -0400
commitf70f095c9096d5e2689e8d79172b37b57a84e51b (patch)
treef58199614f96bd8a52054439ea141bdcbc1410a2 /src/backend/executor/nodeSetOp.c
parent99081c63e40ac6e33c83406b0958aa9426193fea (diff)
downloadpostgresql-f70f095c9096d5e2689e8d79172b37b57a84e51b.tar.gz
postgresql-f70f095c9096d5e2689e8d79172b37b57a84e51b.zip
Allow new relmapper entries when allow_system_table_mods is true.
This restores the pre-9.0 situation that it's possible to add new indexes on pg_class and other mapped-but-not-shared catalogs, so long as you broke the glass and flipped the big red Dont-Touch-Me switch. As before, there are a lot of gotchas, and you'd have to be pretty desperate to try this on a production database; but there doesn't seem to be a reason for relmapper.c to be preventing such things all by itself. Per experimentation with a case suggested by Cody Cutrer.
Diffstat (limited to 'src/backend/executor/nodeSetOp.c')
0 files changed, 0 insertions, 0 deletions