| From: | Jayadevan M <maymala(dot)jayadevan(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Refresh Materialized View |
| Date: | 2014-01-01 13:17:47 |
| Message-ID: | CAFS1N4iGnnDwnmNuRVd1rbKecxHVZyADmQr81eyscA+Byo9MDQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
To answer my own question, I saw this thread -
http://postgresql.1045698.n5.nabble.com/Efficiency-of-materialized-views-refresh-in-9-3-td5762618.html
I think that does answer my questions. Nothing has changed?
Regards,
Jayadevan
On Wed, Jan 1, 2014 at 6:42 PM, Jayadevan M <maymala(dot)jayadevan(at)gmail(dot)com>wrote:
> Hello all,
> A few questions about materialized views.
> When I refresh a materialized view, is it a DELETE/INSERT behind the
> scenes?
> Do we need to vacuum to reclaim space?
> If a query is executed against the view when the refresh is happening,
> will the query see the data before the refresh started?
> Does the refresh result in exclusive locking?
> Regards,
> Jayadevan
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bricklen | 2014-01-01 16:45:54 | Re: How to delete completely duplicate rows |
| Previous Message | Jayadevan M | 2014-01-01 13:12:21 | Refresh Materialized View |