RE: Use of system indexes

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: Use of system indexes
Date: 2000-06-07 06:19:45
Message-ID: 000301bfd048$60186f20$2801007e@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: pgsql-hackers-owner(at)hub(dot)org [mailto:pgsql-hackers-owner(at)hub(dot)org]On
> Behalf Of Bruce Momjian
>
> I am looking at how the system indexes are used.
>
> In the past, I went through and changed all system table lookups that
> return a single value into system cache lookups.
>
> I now see several cases where we are doing heap scans of system tables,
> rather than using indexes. There are cases that can return several
> rows, so we can't use the cache. However, we could use index scans
> rather than heap scans.
>

[snip]

>
> I can start fixing them, but as I remember, someone was thinking of
> making heap/index scans use the same interface. Can I get a status on
> that?
>

In my trial implementation of ALTER TABLE DROP COLUMN in command.c,
there is a trial using
systable_beginscan(),systable_endscan(),systable_getnext()
functions.
However there would better unification of system table scan.

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2000-06-07 06:31:24 OFFTOPIC: SQL book
Previous Message Bruce Momjian 2000-06-07 04:23:50 Look at heap_beginscan()