From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Jan Wieck <jwieck(at)debis(dot)com> |
Cc: | maillist(at)candle(dot)pha(dot)pa(dot)us, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |
Date: | 1998-02-24 15:47:45 |
Message-ID: | Pine.NEB.3.95.980224104709.29869O-100000@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 24 Feb 1998, Jan Wieck wrote:
> >
> > On Tue, 24 Feb 1998, Bruce Momjian wrote:
> >
> > > > 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...
> > >
> > > Good. I didn't want the db_ namespace pollution. I will call it
> > > pg_user_no_passwd, and make it a view, not a rule. Is that OK with
> > > everyone?
> >
> > Works for me...
>
> How? When I create a view the way Bruce explained (update pg_class),
> my backend crashes on SELECT FROM view during the rewrite. For some
> reason the rewrite handler cannot get the rule locks correctly.
Ppl are taking me a slight bit too literally :( "Works for
me"...I like the idea...not necessarily implemented it though :)
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1998-02-24 15:58:07 | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |
Previous Message | Jan Wieck | 1998-02-24 15:45:00 | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |