From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | gerald(at)interface-business(dot)de |
Cc: | pgsql-general <pgsql-general(at)postgreSQL(dot)org>, Carlos Vicente Altamirano <altacar(at)redes(dot)unam(dot)mx>, Charles Tassell <ctassell(at)isn(dot)net> |
Subject: | Re: [GENERAL] users in Postgresql |
Date: | 1999-11-02 17:34:17 |
Message-ID: | Pine.GSO.4.02A.9911021830420.19808-100000@Hermelin.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
May Tom (or anyone) correct me if I'm wrong, but I think this is what's
going on:
The contents of the pg_shadow table are written through to a file on disk
called pg_pwd, so all the backends can easily access it. However, this
write through is not automatic. The create user and alter user commands
take care of that, but if you update pg_shadow directly, your changes will
not be seen by currently active backends.
-Peter
On Tue, 2 Nov 1999 postgres(at)taifun(dot)interface-business(dot)de wrote:
> > Btw., although direct UPDATEs to pg_shadow will seemingly succeed, you do
> > not want to do that. That's a bug.
>
> Peter, would you explain your statement please!
>
> Why somebody is able to UPDATE pg_shadow to create an user if that's a bug?
> And _why_ that's a bug?
>
> Gerald
>
>
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Broytmann | 1999-11-02 17:45:47 | Postgres database on RAM disk - the article in LinuxFocus |
Previous Message | postgres | 1999-11-02 16:34:34 | Re: [GENERAL] users in Postgresql |
From | Date | Subject | |
---|---|---|---|
Next Message | Marcin Grondecki | 1999-11-02 17:49:35 | Re: [GENERAL] users in Postgresql |
Previous Message | Peter Mount | 1999-11-02 16:58:20 | RE: [HACKERS] 6.5.3 is ready |