Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'
Date
Msg-id Pine.BSF.3.96.980224003627.230N-100000@thelab.hub.org
Whole thread Raw
In response to Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'  (Bruce Momjian <maillist@candle.pha.pa.us>)
Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'  (Peter T Mount <psqlhack@maidast.demon.co.uk>)
List pgsql-hackers
On Mon, 23 Feb 1998, Bruce Momjian wrote:

> >
> > On Mon, 23 Feb 1998, Bruce Momjian wrote:
> >
> > >
> > > Can I suggest pgview_ then?  Another problem is that a \d on an empty
> > > database, \d is going to show this view, isn't it.  Kind of strange to
> > > me.
> >
> >     I modified psql already such that:
> >
> >     relname !~ '^[pd][bg]_'
> >
> >     is ignored :)
>
> I still disagree.  Why not keep the system stuff pg_?  This can be done,
> and it keeps things consistent.  The above check also finds pb_ and dg_.

    Actually, I'm not married to db_* for views...it was a "quick fix"
to ensure that things still worked.  Whatever we decide on, both Julie and
Peter, at a minimum, need to know relatively soon.  I know in Julie's
case, she does do a call to pg_user...I let her know tonight that she
needs to change it to db_user, for the *current* code...

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: initdb problem
Next
From: Brett McCormick
Date:
Subject: Re: [HACKERS] Views on aggregates - need assistence