Re: BUG #4688: Bug in cache. - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4688: Bug in cache.
Date
Msg-id 11309.1236094663@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #4688: Bug in cache.  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: BUG #4688: Bug in cache.  (Guillaume Smet <guillaume.smet@gmail.com>)
Re: BUG #4688: Bug in cache.  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-bugs
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Tom Lane wrote:
>> Although this qualifies as pilot error (superusers are expected to know
>> what they're doing), should we attempt to prevent the case?

> We can't detect binary-incompatibility in general, so I presume you
> meant just for the case of composite types. Hmm, I guess we could do it
> in that case.

Right, I was envisioning "if both types are composite and there's no
function supplied, throw error".

> I believe the command has been like that for a long time, and this is
> the first time someone managed to shoot one's foot.

True.  Maybe it's not worth the trouble.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #4688: Bug in cache.
Next
From: Guillaume Smet
Date:
Subject: Re: BUG #4688: Bug in cache.