| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: counting algorithm for incremental matview maintenance |
| Date: | 2013-05-15 16:33:11 |
| Message-ID: | 1368635591.85160.YahooMailNeo@web162902.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> #1 issue I have with current matview functionality is locking.
> currently refresh takes out an access exclusive lock. so,
> question is, do you think your proposal will be such that it will
> no longer require taking out full lock for refresh purposes
> (either incremental or otherwise)?
The right thread for *that* question is "Differential
(transactional) REFRESH"; however, I might as well say here that I
don't think we want to get rid of the (faster) version that just
replaces the current heap when we add the (slower) option to
REFRESH it transactionally.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2013-05-15 17:20:30 | Re: counting algorithm for incremental matview maintenance |
| Previous Message | Merlin Moncure | 2013-05-15 16:12:06 | Re: counting algorithm for incremental matview maintenance |