| From: | Michael Hanna <zen(at)hwcn(dot)org> |
|---|---|
| To: | "Mendola Gaetano" <mendola(at)bigfoot(dot)com> |
| Cc: | "pgsql-novice" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: authentication questions |
| Date: | 2003-06-27 12:58:15 |
| Message-ID: | 04613F7D-A89F-11D7-84B3-00039308EB2C@hwcn.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
OK, but what if you have thousands of users in your pg_shadow table?
Can postgreSQL handle such a load?
Michael
On Friday, June 27, 2003, at 05:48 AM, Mendola Gaetano wrote:
>
> In that way you have less controll on who is using the DB,
> for example you can not use current_user in order to know
> who is doing the query and you can not use the privileges on
> tables, stored procedure, views.....
> and last but not least why you are aware about "do not fill the
> pg_shadow"?
>
>
> Regards
> Gaetano Mendola
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if
> your
> joining column's datatypes do not match
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nabil Sayegh | 2003-06-27 13:10:35 | Re: Address Table |
| Previous Message | Rory Campbell-Lange | 2003-06-27 12:20:39 | SELECT too complex? |