Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Jan Wieck <jwieck(at)debis(dot)com>
Cc: PostgreSQL HACKERS <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'
Date: 1998-02-24 13:14:11
Message-ID: Pine.NEB.3.95.980224081158.29869F-100000@hub.org (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, 24 Feb 1998, Jan Wieck wrote:

>         CREATE TABLE xpg_usr (
>             usename         name,
>             usesysid        int4,
>             usecreatedb     bool,
>             usetrace        bool,
>             usesuper        bool,
>             usecatupd       bool,
>             passwd          text,
>             valuntil        abstime);
> 
>         UPDATE pg_class SET relname = 'pg_usr'
>             WHERE relname = 'xpg_usr';
> 
>         CREATE RULE _RETpg_usr AS ON SELECT TO pg_usr
>             DO INSTEAD
>             SELECT usename, usesysid, usecreatedb,
>                    usetrace, usesuper, usecatupd,
>                    '********'::text as passwd, valuntil
>                    FROM pg_user;
> 
>         REVOKE ALL ON pg_user FROM public;

	Okay, just so that I don't mess things up in the translation...do
you want to send me an appropriate patch for this?

> >     But as it was done  in  most  UN*X's,  could  we  rename  the
> >     pg_user  containing  the  password  into  pg_shadow  and then
> >     create a view pg_user that just stars out the password field?
> >     This  way  no  existing  application  code (not even the JDBC
> >     etc.) needs any  changes,  except  for  the  createuser  etc.
> >     tools that always get installed with the new release.
> 
>     Still vote for this. And as soon as  we  finally  choose  one
>     name  for  the public pg_user view we must fix createuser.sh,
>     createdb.sh and so on to make  their  checks  on  the  public
>     accessible view so they still print the proper error messages
>     instead of

	No arguments here...can you include this as part of your patch
too?




In response to

Responses

pgsql-hackers by date

Next:From: Jan WieckDate: 1998-02-24 13:23:22
Subject: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'
Previous:From: Jan WieckDate: 1998-02-24 12:46:06
Subject: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group