> ok, thats ridiculous, isn't it. so now its time to find a compromise. You don't understand how sales people pitch our products. We deal with financial data and our customers are extremely sensitive to even imagining that their data will co-reside with that of their competitors who also are our customers. A typical fear mongering Q from them "what if due to a bug in your s/w, our competitors end up looking at our data" or something like that. That's why schema level vs db level discussion. Just a reminder, I started this thread to learn more on the technical drawbacks of choosing either option. For example, in SQL Server, having multiple databases in an instance does not mean more significantly pressure on resources (as compared to multiple schemas). In DB2 it does since many resources like cache (buffers) are db specific. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
