Re: pgsql: Remove pg_class.relhaspkey

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Remove pg_class.relhaspkey
Date: 2018-03-15 13:35:35
Message-ID: 15389.1521120935@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Well, maybe we should dictate policy that it must be possible to
> pg_upgrade this database too; then we'll just have to work so that it
> always works. I have fixed the current problem and I'm open to the idea
> of keeping it working.

Name of the matview now seems a bit confusing ...

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2018-03-15 15:36:52 pgsql: Pass additional arguments to a couple of grouping-related functi
Previous Message Alvaro Herrera 2018-03-15 13:03:46 Re: pgsql: Move strtoint() to common