Skip site navigation (1) Skip section navigation (2)

pgsql: Allow new relmapper entries when allow_system_table_mods istrue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Allow new relmapper entries when allow_system_table_mods istrue
Date: 2012-03-21 18:09:54
Message-ID: E1SAPys-00028q-0b@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
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.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/f70f095c9096d5e2689e8d79172b37b57a84e51b

Modified Files
--------------
src/backend/utils/cache/relmapper.c |    7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)

pgsql-committers by date

Next:From: Robert HaasDate: 2012-03-21 18:53:04
Subject: pgsql: Doc updates for index-only scans.
Previous:From: Tom LaneDate: 2012-03-21 17:05:41
Subject: pgsql: Back-patch contrib/vacuumlo's new -l (limit) option into 9.0and

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group