| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] DOC: catalog.sgml |
| Date: | 2006-09-01 16:36:11 |
| Message-ID: | 20060901163611.GG3755@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> > I little bit enhanced overview catalog tables. I added two new columns.
> > First one is OID of catalog table and second one contains attributes
> > which determine if the table is bootstrap, with oid and global.
>
> Why is this a good idea? It seems like mere clutter.
What's "global"? A maybe-useful flag would be telling that a table is
shared. Is that it? Mind you, it's not useful to me because I know
which tables are shared, but I guess for someone not so familiar with
the catalogs it could have some use.
The OIDs may be useful to people inspecting pg_depend, for example; but
then, it's foolish not to be using regclass in that case.
Whether a table is "bootstrap" or not doesn't seem useful to me.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-09-01 16:45:05 | Re: [GENERAL] Thought provoking piece on NetBSD |
| Previous Message | Jeroen T. Vermeulen | 2006-09-01 16:35:46 | Re: Prepared statements considered harmful |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-09-01 17:30:55 | Predicate Locking |
| Previous Message | Bruno Wolff III | 2006-09-01 15:07:06 | Re: [PATCHES] Backend SSL configuration enhancement |