Phil Sorber writes:
> I compiled 9.1 stable head and tested it out. You are correct my
> example no longer works there because of the patch that stopped the
> auto-generated types from becoming dependencies of the extension. In
> fact, the cascade no longer works even if I don't remove the table o
On Mon, Nov 28, 2011 at 4:10 PM, Tom Lane wrote:
> Phil Sorber writes:
>> I am still able to reproduce the "ERROR: cache lookup failed for extension
>> x" if I use an explicit 'drop extension'. I am unsure how I can
>> reverse the state it is now in. I assume there is some system catalog
>>
Phil Sorber writes:
> I am still able to reproduce the "ERROR: cache lookup failed for extension
> x" if I use an explicit 'drop extension'. I am unsure how I can
> reverse the state it is now in. I assume there is some system catalog
> I can edit that will fix it?
I think you have some dang
On Mon, Nov 28, 2011 at 3:12 PM, Tom Lane wrote:
> Phil Sorber writes:
>> I stumbled upon this situation when playing with extension upgrades.
>> The problem I was having was that auto-generated datatypes were also
>> being added to the extension and it wasn't obvious this was happening.
>> I kno
Phil Sorber writes:
> I stumbled upon this situation when playing with extension upgrades.
> The problem I was having was that auto-generated datatypes were also
> being added to the extension and it wasn't obvious this was happening.
> I know this has been changed in 9.1 stable and in master.
I
I stumbled upon this situation when playing with extension upgrades.
The problem I was having was that auto-generated datatypes were also
being added to the extension and it wasn't obvious this was happening.
I know this has been changed in 9.1 stable and in master.
What happened was that I was ab