Re: BUG #4688: Bug in cache.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Oleg <serovOv(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4688: Bug in cache.
Date: 2009-03-03 15:10:02
Message-ID: 10782.1236093002@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Oleg wrote:
>> CREATE CAST (tmp_table AS composite_ad_texts)
>> WITHOUT FUNCTION AS ASSIGNMENT;

> "WITHOUT FUNCTION" can only be used when both types are binary
> compatible. You might think that two composite types with the same
> fields are, but they're not: we store the OID of the composite type in
> the records.

Although this qualifies as pilot error (superusers are expected to know
what they're doing), should we attempt to prevent the case? It doesn't
seem like a tremendously unlikely mistake to make, and AFAICS there is
no easy way to recover your data once you've done it.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2009-03-03 15:28:43 Re: BUG #4688: Bug in cache.
Previous Message Heikki Linnakangas 2009-03-03 11:21:30 Re: BUG #4688: Bug in cache.