Re: pgsql: Remove pg_class.relhaspkey - Mailing list pgsql-committers

From Alvaro Herrera
Subject Re: pgsql: Remove pg_class.relhaspkey
Date
Msg-id 20180314231132.4ac5hlxhs7m2xbhg@alvherre.pgsql
Whole thread Raw
In response to Re: pgsql: Remove pg_class.relhaspkey  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Remove pg_class.relhaspkey
List pgsql-committers
Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
> > Basing an MV on pg_class could always be difficult for pg_upgrade. Maybe
> > that's not a brilliant thing to do in a test (or maybe the test should drop
> > the MV after it's done).
> 
> OH.  Is that what it's doing?  The cause of the failure is immediately
> obvious then.  pg_class now lacks a relhaspkey column, but the matview
> is still dependent on one being there.
> 
> I concur that this is not well-considered test design.

It seems very strange to me that the test_ddl_deparse database would be
used by a pg_upgrade test, but OK.  I'll change it.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Remove pg_class.relhaspkey
Next
From: Erik Rijkers
Date:
Subject: Re: pgsql: Support INOUT arguments in procedures