AW: "setuid" functions, a solution to the RI privilege problem

> (With 7.2 I plan to get rid of pg_shadow.usesysid and
> identify users via
> pg_shadow.oid and the superuser oid will be hard-coded into
> include/catalog/pg_shadow.h, so at that point they will work.)

Imho it is fine to get rid of the usesysid in our internal authorization
system,
but we should not get rid of the only field that can tie a db user
to an os user. Imho we should not do a "by name" lookup
and eliminate the field. The extra field adds additional flexibility,
like using one os user for many db users, or using different names
for os users.

In the long run we will need a tie to os users for os level setuid user
functions.

Andreas