| From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Toby Corkindale <toby(dot)corkindale(at)strategicdata(dot)com(dot)au>, Alban Hertroys <haramrae(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Many, many materialised views - Performance? |
| Date: | 2013-10-09 11:35:12 |
| Message-ID: | 20131009073512.05fc3918e1902aa65d47157b@potentialtech.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 8 Oct 2013 19:08:45 -0700 (PDT) Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> > In this instance, we have a lot of queries that build certain aggregate
> > results, which are very slow. The queries were initially all implemented
> > as views, but then we started doing a type of materialising of our own,
> > turning them into tables with CREATE TABLE AS SELECT ....
> > This does make the results very fast to access now, but the side effect
> > is a vast number of (very small) tables.
I missed the start of this thread, so apologies if my suggestion is off-base.
When there are lots of tables, I've seen performance improvements from
distributing the tables through schemas. It seems to improve name
resolution performance.
--
Bill Moran <wmoran(at)potentialtech(dot)com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | janek12 | 2013-10-09 11:35:41 | Re: pg_similarity |
| Previous Message | Jesse Long | 2013-10-09 11:02:05 | Re: Incorrect index being used |