From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Cc: Chris <chris@bitmead.com>
Subject: relhasindex(was RE: [HACKERS] Proposed Changes to PostgreSQL)
Date: Fri, 4 Feb 2000 09:16:46 +0900
Message-ID: <000201bf6ea5$1f8a9be0$2801007e@tpf.co.jp> (raw)
In-Reply-To: <200002031237.HAA21220@candle.pha.pa.us>
> -----Original Message-----
> From: owner-pgsql-hackers@postgreSQL.org
> [mailto:owner-pgsql-hackers@postgreSQL.org]On Behalf Of Bruce Momjian
>
> > Bruce Momjian wrote:
> >
> > > > Well I see that pg_class has columns like "relhasindex". If
> we added a
> > > > "relhassubclass", the overhead should be unmeasureable.
> > >
> > > Yes, but how do you keep that accurate? If I add indexes, then drop
> > > them, does relhasindex go to false.
> >
> > I don't know. Does it?
>
> Let me add that to the TODO list.
>
> >
> > >Could you do that for relhassubclass?
> >
> > If we made it relnumsubclasses and incremented/decremented on
> > CREATE/DROP, it seems easy in theory.
>
> Yes, that would work. Seems hasindex has problems.
>
This posting may be off the point,sorry.
Isn't relhasindex a kind of item that we can live without it ?
I proposed to change the use of this item in [[HACKERS] Index
recreation in vacuum]. Though I have heard no clear objection,
I want to confirm again. My proposal is as follows.
1) DDL commands don't rely on relhasindex.
2) DML commands don't take indexes into account if
relhasindex is set to false.
3) REINDEX command and vacuum with REINDEX option
sets this flag to false at the beginning and sets it to true
when recreation of all indexes completed.
Comments ?
Regards.
Hiroshi Inoue
Inoue@tpf.co.jp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: Inoue@tpf.co.jp, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org, chris@bitmead.com
Subject: Re: relhasindex(was RE: [HACKERS] Proposed Changes to PostgreSQL)
In-Reply-To: <000201bf6ea5$1f8a9be0$2801007e@tpf.co.jp>
References: <200002031237.HAA21220@candle.pha.pa.us> <000201bf6ea5$1f8a9be0$2801007e@tpf.co.jp>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox