>>> Tom Lane <[email protected]> wrote: > We have seen no evidence that anyone has a worked-out > set of design rules that make a SE-Postgres database secure against > these issues, so the whole thing is pie in the sky. I've seen several mentions of the rule "Don't use a column containing data you want to secure as part of the primary key." mentioned several times in these threads. I think that just might be the complete set. Can anyone show that it's not? -Kevin
-- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
