Return-Path: owner-postman
Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with SMTP id BAA03586 for postgres-redist; Thu, 21 Jul 1994 01:31:33 -0700
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199407210831.BAA03586@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from faerie.CS.Berkeley.EDU (faerie.CS.Berkeley.EDU [128.32.149.14]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with ESMTP id BAA03576 for <postgres@postgres.Berkeley.EDU>; Thu, 21 Jul 1994 01:31:27 -0700
Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by faerie.CS.Berkeley.EDU (8.6.4/8.1B) with SMTP id BAA14595; Thu, 21 Jul 1994 01:31:06 -0700
Message-Id: <199407210831.BAA14595@faerie.CS.Berkeley.EDU>
X-Authentication-Warning: faerie.CS.Berkeley.EDU: Host localhost.Berkeley.EDU didn't use HELO protocol
From: aoki@CS.Berkeley.EDU (Paul M. Aoki)
To: wolf@molout.tutkie.tut.ac.jp (Wolf-D. Ihlenfeldt)
Cc: postgres@postgres.Berkeley.EDU
Subject: Re: Private indices on system catalogs ? 
Reply-To: aoki@CS.Berkeley.EDU (Paul M. Aoki)
In-reply-to: Your message of Tue, 19 Jul 94 19:59:00 jst 
	     <9407191059.AA05521@molout.tutkie.tut.ac.jp> 
Date: Thu, 21 Jul 94 01:31:05 -0700
X-Sender: aoki@postgres.Berkeley.EDU
Resent-To: postgres-redist@postgres.Berkeley.EDU
X-Mts: smtp
Resent-Date: Thu, 21 Jul 94 01:31:28 -0700
Resent-XMts: smtp

wolf@molout.tutkie.tut.ac.jp (Wolf-D. Ihlenfeldt) writes:
> and rebuilding it cures the symptoms, but why is the pg_attribute
> index not updated when new attributes are added (which happens when
> I create new relations). Is it because the index in mine, not 
> belonging to user postgres ? Or are there other arcane reasons ?

for user indices, index update is done by the query executor.
whenever you insert a new row, the executor updates all of
the indices for you.

the code that inserts new data into the system catalogs (e.g.,
when you "create" a table, the code that inserts entries into 
pg_class and pg_attribute) knows exactly what indices are 
"supposed" to be defined and updates only those indices.  that 
is, it bypasses the query executor and makes direct access 
method calls based on some hardwired code.

the hash am does seem to be pretty fast but nobody here ever had 
a chance to beat on it enough to instill a lot of confidence in it.
--
  Paul M. Aoki          |  University of California at Berkeley
  aoki@CS.Berkeley.EDU  |  Dept. of EECS, Computer Science Division (#1776) 
                        |  Berkeley, CA 94720-1776

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"

   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================