Skip site navigation (1) Skip section navigation (2)

Re: pg_upgrade and relkind filtering

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade and relkind filtering
Date: 2011-12-07 06:16:25
Message-ID: 10514.1323238585@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Dec 5, 2011 at 5:06 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> Pg_upgrade has the following check to make sure the cluster is safe for
>> upgrading:
>> 
>> What types, other than views, can we skip in this query?

> It's not obvious to me that anything other than a table or index would matter.

You'd better complain about composite types too, since one of them could
be a column in a table.  (Unless you want to test to see whether it
actually is stored anywhere, but that seems like way overkill for this.)

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2011-12-07 07:23:32
Subject: Re: review: CHECK FUNCTION statement
Previous:From: Robert HaasDate: 2011-12-07 03:45:20
Subject: Re: Inlining comparators as a performance optimisation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group