Re: refresh materialized view concurrently - Mailing list pgsql-hackers

From Tom Lane
Subject Re: refresh materialized view concurrently
Date
Msg-id 24377.1372864112@sss.pgh.pa.us
Whole thread Raw
In response to Re: refresh materialized view concurrently  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: refresh materialized view concurrently
Re: refresh materialized view concurrently
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Jul 3, 2013 at 10:47 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Are we somehow not going through ExecOpenIndices?

> I dunno.  I just did a quick black-box test:

> CREATE TABLE foo (a int primary key);
> BEGIN;
> INSERT INTO foo VALUES (1);
> SELECT relation::regclass, locktype, mode, granted FROM pg_locks;

> I get:

>  relation |   locktype    |       mode       | granted
> ----------+---------------+------------------+---------
>  pg_locks | relation      | AccessShareLock  | t
>  foo      | relation      | RowExclusiveLock | t
>           | virtualxid    | ExclusiveLock    | t
>           | transactionid | ExclusiveLock    | t

> No foo_pkey anywhere.

That proves nothing, as we don't keep such locks after the query
(and there's no reason to AFAICS).  See ExecCloseIndices.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Add more regression tests for ASYNC
Next
From: Ian Lawrence Barwick
Date:
Subject: (trivial patch) remove superfluous semicolons from pg_dump