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

Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: crystal <crystal_lium(at)163(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390
Date: 2008-07-09 15:26:18
Message-ID: 13463.1215617178@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> This patch fixes it, but I'm not sure if it breaks some other case (not
> awake enough yet I think).

AFAICS this patch destroys the entire reason for having the
performMultipleDeletion mechanism in the first place, which was to not
fail in the RESTRICT case when there were dependencies between objects
owned by different users.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2008-07-09 15:32:41
Subject: Re: BUG #4289: drop owned by report ERROR: cache lookupfailed for relation 16390
Previous:From: Tom LaneDate: 2008-07-09 15:18:24
Subject: Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390

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