| From: | "Herr Dumont" <dumont(at)gmx(dot)net> | 
|---|---|
| To: | <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | password change / table creation | 
| Date: | 2000-02-17 23:40:23 | 
| Message-ID: | 001901bf79a0$87014980$b0e006d5@planet | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
There are two questions in the pgsql-admin mailing list which are very often
asked, but nobody seems to have a reasonable answer to these.
So I decided to post them here and I hope anyone can help me (and many
others) !
    - Can a PostgreSQL user change his own password without having
      "usesuper" set to 't' in pg_shadow ?
      I think this should be possible with a PostgreSQL C function (or
      PL/Tcl) which alters the "passwd" attribute of the pg_shadow table and
      after that copies the contents of this table to the pg_pwd ASCII file
      (and generates an empty pg_pwd.reload).
      But I have no idea how to manipulate and copy tables within PostgreSQL
      C functions.
      Does anybody know if there is already such a function or any other way
      to achieve the above mentioned functionality ?
    - Can the Postgres superuser prevent a user from creating tables in any
      database the user likes to ?
      It would be good to have a way to restrict the use of the "CREATE
      TABLE" SQL statement so that a user can only create tables in
      databases he is explicitly allowed to.
Does anyone have an idea how to solve this problem ?
If these two features are not yet implemented I would suggest to think about
implementing them, because I (and many other people) would consider them
as important, especially in practical use.
Please let me know !
Thank you very much
RP. Dumont
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-02-17 23:40:41 | Re: [HACKERS] Almost there on column aliases | 
| Previous Message | Chris Bitmead | 2000-02-17 23:38:42 | Re: [HACKERS] FYI: BNF for SQL93 and SQL-3 |