From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Richards <miker(at)scifair(dot)acadiau(dot)ca> |
Cc: | pgsql-sql(at)postgreSQL(dot)org, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] entries in pg_shadow |
Date: | 1999-08-29 01:00:46 |
Message-ID: | 9799.935888446@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
Michael Richards <miker(at)scifair(dot)acadiau(dot)ca> writes:
> The entries entered in pg_shadow haven't ever worked for me. I've tried a
> number of times without success. If I update a user in there and set a
> password for them:
IIRC, the only way to set a password that actually works is ALTER USER.
The reason direct SQL hacking on pg_shadow doesn't work is that
pg_shadow isn't what the postmaster looks at (the PM itself can't do
database operations without getting into possible deadlock situations).
There's a flat text file somewhere that contains the Real Info. ALTER
USER and friends know to rewrite the flat file after updating pg_shadow.
This is documented somewhere, I think, but not nearly prominently
enough...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Constantin Teodorescu | 1999-08-29 07:36:30 | Cluster on (index-name) loose NOT NULL properties |
Previous Message | Tom Lane | 1999-08-29 00:54:23 | Re: [HACKERS] Quoting in stored procedures |
From | Date | Subject | |
---|---|---|---|
Next Message | Dipl.-Ing. Thomas Schallar | 1999-08-29 15:43:04 | SELECT multiple tables with same fields |
Previous Message | Tom Lane | 1999-08-29 00:46:40 | Re: [SQL] indexes using datetime |