Re: Broken HOT chains in system catalogs

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

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?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-04-15 19:35:13 Re: Broken HOT chains in system catalogs
Previous Message Tom Lane 2011-04-15 19:13:04 Re: Single client performance on trivial SELECTs