> It might make more sense to use your own table of users and hashed
> passwords
> rather than postgres'. This would depend somewhat on the overlap of users
> who
> are using your application and those who connect directly to the database.
> If there isn't much overlap, having a separate table is probably better.
Using own table requires storing Postgres user name and password in client
computer. Thus this information is available to virtually everyone haveing
access to client computer.
So this is very bad idea and should avoided at all.
Andrus.
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
