From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) |
Cc: | jwieck(at)debis(dot)com, scrappy(at)hub(dot)org, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |
Date: | 1998-02-24 19:52:37 |
Message-ID: | 199802241952.OAA14617@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> > > > 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 :)
> >
> > I already have the pg_shadow + pg_user-view diff ready. Works
> > really! Must run a regression test and send it after that
> > succeeded. It updates createuser, destroyuser and initdb too.
>
> Great news. Go for it. Please back out the psql db_ changes and any
> initdb stuff we don't need anymore.
Again, this is very good. I had not thought of making pg_user a
different name, but that is the perfect solution. Here is a case where
many heads get a nice solution. PostgreSQL is full of those areas where
people get good ideas for certain areas, and the whole project gets
better.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-02-24 19:56:58 | Re: [HACKERS] some problems with new locking code |
Previous Message | Peter T Mount | 1998-02-24 19:31:44 | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |