Re: REASSIGN OWNED doesn't for all objects, ALTER FUNCTION seems to fix it

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: pgsql-general(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: REASSIGN OWNED doesn't for all objects, ALTER FUNCTION seems to fix it
Date: 2011-04-20 22:03:02
Message-ID: 201104210003.03179.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

Op woensdag 20 april 2011, schreef Tom Lane:
> Actually, now that I think about it, 8.4 didn't allow on-the-fly
> reindexing of shared catalogs anyway. So that couldn't be your problem
> even if the test had shown the indexes didn't match the catalog. But
> it seems the rows actually disappeared from the catalog, and I have no
> idea what would've caused that.

ok, clear

should we even try to get them back by generating them somehow?

we're planning to upgrade to v9 in a month or so....

also: would there be any reason you can think of why using alter function in
the current version in order to correct this situation would have a negative
side-effect?

--
Best,

Frank.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2011-04-20 22:18:40 Re: REASSIGN OWNED doesn't for all objects, ALTER FUNCTION seems to fix it
Previous Message Tom Lane 2011-04-20 21:31:39 Re: REASSIGN OWNED doesn't for all objects, ALTER FUNCTION seems to fix it