[DOCS] mark wath catalogs are shared - was:(Re: [NOVICE] which database to login to to create global users?)
On 1/3/06, pres <[EMAIL PROTECTED]> wrote: > hello tom, > > > > See also the documentation on the system catalogs: > > http://www.postgresql.org/docs/8.1/static/catalogs.html > > The description of each catalog takes care to mention it if the catalog > > is shared across databases. > > > > regards, tom lane > > > > > i'm not yet sure if/where we can make enduser requests, but in reading the > documentation's "System Catalogs" section you'd pointed me to, i, of course, > find: > > > > "... A few catalogs are physically shared across all databases in a cluster; > these are noted in the descriptions of the individual catalogs. > > Table 42-1. System Catalogs..." > > i would find it helpful if Table 42-1 included a column that identified > whehter each catalog is shared or not. convenient, but given that the > documentation does contain it, not necessary. > > simply, it would be nice to see it as an overview. > > thank you again. > > pres is this acceptable or usefull? if so, i can do it after work... -- regards, Jaime Casanova (DBA: DataBase Aniquilator ;) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [DOCS] mark wath catalogs are shared - was:(Re: [NOVICE] which database to login to to create global users?)
Jaime Casanova <[EMAIL PROTECTED]> writes: > On 1/3/06, pres <[EMAIL PROTECTED]> wrote: >> i would find it helpful if Table 42-1 included a column that identified >> whehter each catalog is shared or not. convenient, but given that the >> documentation does contain it, not necessary. > is this acceptable or usefull? if so, i can do it after work... It seems like clutter to me. Whether a catalog is shared or not is not necessarily the first thing you want to know about it. regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [DOCS] mark wath catalogs are shared - was:(Re: [NOVICE] which database
Tom Lane wrote: > Jaime Casanova <[EMAIL PROTECTED]> writes: > > On 1/3/06, pres <[EMAIL PROTECTED]> wrote: > >> i would find it helpful if Table 42-1 included a column that identified > >> whehter each catalog is shared or not. convenient, but given that the > >> documentation does contain it, not necessary. > > > is this acceptable or usefull? if so, i can do it after work... > > It seems like clutter to me. Whether a catalog is shared or not is not > necessarily the first thing you want to know about it. I am thinking the table should be split into two, one for the global tables, and another for the db-local tables. I don't think we make it clear enough which tables are global. -- Bruce Momjian| http://candle.pha.pa.us [email protected] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [DOCS] mark wath catalogs are shared - was:(Re: [NOVICE] which database to login to to create global users?)
Bruce Momjian writes: > Tom Lane wrote: >> It seems like clutter to me. Whether a catalog is shared or not is not >> necessarily the first thing you want to know about it. > I am thinking the table should be split into two, one for the global > tables, and another for the db-local tables. That's even worse, as it converts the distinction into something you must know even to look up the table. > I don't think we make it clear enough which tables are global. I think the labels appearing in the per-catalog descriptions are plenty clear. regards, tom lane ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [DOCS] CONSTRAINT syntax in ALTER TABLE
> From: Bruce Momjian [mailto:[EMAIL PROTECTED] > > is (I assume) it would do nothing to help \h ALTER TABLE in > psql. Maybe > > a good compromise would be to include the table_constraint > section of > > the CREATE TABLE syntax in the ALTER TABLE syntax. > > If they created the table, they have already seen the > constraint syntax. > I see no reason to repeat it. The reason I'd repeat it is because when you're going to modify existing constraints, you'll be using ALTER TABLE. Sure, if the user memorized the constraint syntax when they created the table, they won't need extra help. Personally, I usually make use of column-level constraints when writing DDL, so any time I need to use table-level syntax I often have to look something up. That's why I'd like to see the info in \h. If you look at our docs from a newbie standpoint, they're not very easy to use, because it's difficult to find stuff unless you know where to look. If you're looking in the SQL Syntax section, ALTER TABLE is the obvious choice if you need to change something about the table, but it's a PITA to have to refer to other documentation to find the full syntax for the command. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
