Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'
От | jwieck@debis.com (Jan Wieck) |
---|---|
Тема | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |
Дата | |
Msg-id | m0y7MXY-000BFRC@orion.SAPserv.Hamburg.dsh.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' (The Hermit Hacker <scrappy@hub.org>) |
Ответы |
Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'
|
Список | pgsql-hackers |
> > 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. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #======================================== jwieck@debis.com (Jan Wieck) #
В списке pgsql-hackers по дате отправления: