Re: DROP OWNED BY ... CACADE & "could not open relation with OID" error

From: Satoshi Nagayasu <snaga(at)uptime(dot)jp>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: DROP OWNED BY ... CACADE & "could not open relation with OID" error
Date: 2016-07-21 05:12:31
Message-ID: CAA8sozff-1Mx6LdmfT3eK00=jLEv=qsEf2w7+Ci56Py1Rq3vJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2016-07-21 13:53 GMT+09:00 Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:
> Satoshi Nagayasu wrote:
>> Hi,
>>
>> I have been trying MADlib [1], a machine-learning library for PostgreSQL,
>> and when I was tying it on 9.5 and 9.6beta2, I often got following
>> error on my box.
>>
>> ------------------------------------
>> madpack.py : ERROR : SQL command failed:
>> SQL: DROP OWNED BY madlib_19_installcheck CASCADE;
>> ERROR: could not open relation with OID 147056
>> ------------------------------------
>>
>> I wonder it could be a PostgreSQL bug or not.
>> AFAIK, this kind of error should not occur during regular SQL command execution,
>> so I guess this is a PostgreSQL bug.
>
> Agreed.
>
>> Should I dig it down deeper to reproduce in a simple procedure?
>
> Yes, please.

Ok. I will try it.

Regards,
--
Satoshi Nagayasu <snaga(at)uptime(dot)jp>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2016-07-21 07:30:46 Re: Oddity in handling of cached plans for FDW queries
Previous Message David Fetter 2016-07-21 04:57:46 PoC: Make it possible to disallow WHERE-less UPDATE and DELETE