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.
> >
> >
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 ac
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, no
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'
> 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 hav
