Re: refresh materialized view concurrently

On Mon, Jun 17, 2013 at 11:21 AM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> Nicolas Barbier <nicolas(dot)barbier(at)gmail(dot)com> wrote:
>> 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.
>
> It means that the index must not use any expressions in the list of
> what it's indexing on -- only column names. Suggestions for better
> wording would be welcome.

Random idea:

ERROR: materialized view \"%s\" does not have a unique key

Perhaps augmented with:

HINT: Create a UNIQUE btree index with no WHERE clause on one or more
columns of the materialized view.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company