From: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: refresh materialized view concurrently |
Date: | 2013-06-21 09:43:23 |
Message-ID: | CAP7QgmnZcQwHFJQzrgpjX2rphjLyPSTG5sfPsMmxZxJ0=7tEGA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 21, 2013 at 2:20 AM, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>wrote:
>
>
>
> On Fri, Jun 14, 2013 at 9:05 AM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
>
>> Attached is a patch for REFRESH MATERIALIZED VIEW CONCURRENTLY for
>> 9.4 CF1. The goal of this patch is to allow a refresh without
>> interfering with concurrent reads, using transactional semantics.
>>
>
> I spent a few hours to review the patch.
>
Oh, BTW, though it is not part of this patch, but I came across this.
! /*
! * We're not using materialized views in the system catalogs.
! */
Assert(!IsSystemRelation(matviewRel));
Of course we don't have builtin matview on system catalog, but it is
possible to create such one by allow_system_table_mods=true, so Assert
doesn't look like good to me.
Thanks,
--
Hitoshi Harada
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-06-21 09:45:56 | Re: refresh materialized view concurrently |
Previous Message | Andres Freund | 2013-06-21 09:41:58 | Re: backend hangs at immediate shutdown (Re: Back-branch update releases coming in a couple weeks) |