From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) |
Cc: | jwieck(at)debis(dot)com, lockhart(at)alumni(dot)caltech(dot)edu, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Rules for 6.4 finished |
Date: | 1998-08-26 09:37:18 |
Message-ID: | m0zBc11-000EBPC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > Another topic is if we should create some more system views
> > at initdb time. I would find views telling ownership and
> > other information readable instead of Oid's very useful. As
> > for pg_rule and pg_view it would be possible to create a view
> > that describes the definition of an index instead of some
> > cryptic numbers. And another one for real tables where
> > indices and views are omitted would also be useful.
>
> Yes, these are good ideas.
>
> --
> Bruce Momjian | 830 Blythe Avenue
I'm running into some naming problems while doing so. Having
pg_table, pg_view etc. as views lets a users assume pg_index
would be one too where to get some information. But pg_index
already exists.
Should I name all of them pgv_... ?
Other databases have many views starting with DBA or SYS on
the other hand. For now I'll start naming them pgv_..., we
could rename them before applying the patch.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Ivar Helbekkmo | 1998-08-26 10:54:10 | Re: [HACKERS] vacuum problem |
Previous Message | Jan Wieck | 1998-08-26 09:23:09 | TODO (was: Re: [HACKERS] Problem with parser) |