From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | pgman(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) |
Cc: | lockhart(at)alumni(dot)caltech(dot)edu, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] 7.0 status request |
Date: | 1999-11-19 19:55:14 |
Message-ID: | m11ou7m-0003kKC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> > > Here are the major open issues for 7.0 that I remember:
> > > Foreign Keys - Jan
> > > WAL - Vadim
> > > Function args - Tom
> > > System indcxes - Bruce
> > > Outer joins and new multi-query parse tree are questionable items for
> > > 7.0.
> >
> > You might include "join syntax", which will be ready even if outer
> > joins are not.
> >
> > Also, didn't some folks express concern that indices on system tables
> > would make the backend more fragile? Did we resolve that issue?
>
> We have indexes on most system tables and it isn't a problem currently.
It is, because a corrupted index on a system table cannot be
corrected by drop/create, as a user defined index could be.
I don't know why and when reindexdb disappeared, but that
script was a last resort for exactly the situation of a
corrupted system index. Let me take a look if this
functionality could easily be recreated.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1999-11-19 20:05:39 | Re: [HACKERS] Curiously confused query parser. |
Previous Message | Tim Holloway | 1999-11-19 19:47:13 | All forked up |