Re: Broken HOT chains in system catalogs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Broken HOT chains in system catalogs
Date: 2011-04-15 19:35:13
Message-ID: 29296.1302896113@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This amounts to assuming that no new indexes get added to system
>> catalogs after initdb, or at least not during concurrent
>> operations wherein indcheckxmin would be important.

> Sounds reasonable, but can we enforce it through locks rather than
> assuming, or isn't there a clear way to do that without risking
> deadlocks?

Well, we already enforce it through the allow_system_table_mods mechanism:

regression=# create index foo on pg_index(indcheckxmin);
ERROR: permission denied: "pg_index" is a system catalog

Yes, you can turn that off if you try hard enough, but it's on your own
head to know the consequences.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-04-15 19:49:32 Re: Broken HOT chains in system catalogs
Previous Message Kevin Grittner 2011-04-15 19:28:55 Re: Broken HOT chains in system catalogs