Re: refresh materialized view concurrently

From: Nicolas Barbier <nicolas(dot)barbier(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: refresh materialized view concurrently
Date: 2013-06-17 13:33:04
Message-ID: CAP-rdTY3C4XV498Z4MtWCTwkmKPNa-RCtLqi=sqvZCeFufh-aw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2013/6/17 Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>:

> + errmsg("concurrent refresh requires a
> unique index on just columns for all rows of the materialized view")));

Maybe my english is failing me here, but I don’t understand the “just” part.

Nicolas

--
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-06-17 14:16:22 PQConnectPoll, connect(2), EWOULDBLOCK and somaxconn
Previous Message Andres Freund 2013-06-17 13:19:13 Re: Support for REINDEX CONCURRENTLY