-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 14 Mar 2008 02:00:39 -0600 Micah Yoder <micah@xxxxxxxxxxxx> wrote: > Maybe it's nuts to consider such a setup (and if you're talking a > major bank it probably is) ... and maybe not. At this point it's > kind of a mental exercise. :-) If you don't have enough control over the application to handle that type of situation, no database is going to serve your purposes. Beyond that, PostgreSQL is one of the most flexible database systems around when it comes to security and my company professionally supports several financial firms using PostgreSQL as their core database. Sincerely, Joshia D. Drake - -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL political pundit | Mocker of Dolphins -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH2n4JATb/zqfZUUQRApakAJ9oJFFVEji72W71G+50bLb7+O90kQCgimwM Rt5kAqM4EvAMHsQ8U1ShKzo= =VdVV -----END PGP SIGNATURE----- -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-general
