From: | John Moore <wx-chase(at)tinyvital(dot)com> |
---|---|
To: | Postgresql Admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | views: performance implication |
Date: | 2002-07-04 18:44:33 |
Message-ID: | 5.1.1.6.2.20020704114303.0497fcc0@pop3.norton.antivirus |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
We hope to use views as a way to give customers odbc based ad-hoc query
access to our database while enforcing security. The reason is that we do
not want to put data into separate tables by customer, but rather use a
customer ID as part of any query criteria on any table.
So the question is: are there any negative performance implications of
doing so (other than the obvious of having more data in a table than is of
interest to the querying customer)? Back in the old days, views were a
performance no-no in Informix, so I want to be sure we aren't setting a big
trap for ourselves.
Thanks in advance.
John Moore
http://www.tinyvital.com/personal.html
UNITED WE STAND
From | Date | Subject | |
---|---|---|---|
Next Message | John Moore | 2002-07-04 18:45:18 | views: performance implication |
Previous Message | Chad R. Larson | 2002-07-04 18:29:32 | Re: Authentication in batch processing |