Re: Refresh Materialized View
От | Jayadevan M |
---|---|
Тема | Re: Refresh Materialized View |
Дата | |
Msg-id | CAFS1N4iGnnDwnmNuRVd1rbKecxHVZyADmQr81eyscA+Byo9MDQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Refresh Materialized View (Jayadevan M <maymala.jayadevan@gmail.com>) |
Ответы |
Re: Refresh Materialized View
|
Список | 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?http://postgresql.1045698.n5.nabble.com/Efficiency-of-materialized-views-refresh-in-9-3-td5762618.html
On Wed, Jan 1, 2014 at 6:42 PM, Jayadevan M <maymala.jayadevan@gmail.com> wrote:
JayadevanDoes the refresh result in exclusive locking?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?
Regards,
В списке pgsql-general по дате отправления: