| From: | Vick Khera <vivek(at)khera(dot)org> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to improve performance in reporting database? |
| Date: | 2010-07-23 19:06:23 |
| Message-ID: | AANLkTinOSWogj1vQ=wCfO4F_9X53Fop9JMBBM0cgDBkY@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jul 22, 2010 at 2:31 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> You can build those manually with PostgreSQL if you really want them:
> http://wiki.postgresql.org/wiki/Materialized_Views
>
Another thing to consider... In our case we use a materialized view to
keep track of counts of various things that are expensive to count,
such as number of members of a specific account, or number of times a
particular URL was viewed. What we end up with is many processes
trying to update the same counter row, and we end up with lots and
lots of lock contention.
Which reminds me... Greg, are you done with your book yet and when can
I get you back in here to help with my locking problems? ;-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2010-07-23 19:08:27 | Re: Finding last checkpoint time |
| Previous Message | Andrus Moor | 2010-07-23 18:51:10 | Re: How to distribute quantity if same product is in multiple rows |