Re: views: performance implication

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: John Moore <postgres(at)tinyvital(dot)com>
Cc: Postgresql Admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: views: performance implication
Date: 2002-07-04 19:50:28
Message-ID: 200207041950.g64JoSr05151@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

John Moore wrote:
> 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.

Views are rewritten as rules for every query issued, so there is little
performance impact except for the complexity of your view (GROUP BY,
aggregates, etc.)

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message John Moore 2002-07-04 20:23:02 Re: Performance impact of record sizes
Previous Message Bruce Momjian 2002-07-04 19:47:28 Re: Performance impact of record sizes