Re: 7.5 backend crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gaetano Mendola <mendola(at)bigfoot(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 7.5 backend crash
Date: 2004-07-26 06:05:04
Message-ID: 19443.1090821904@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gaetano Mendola <mendola(at)bigfoot(dot)com> writes:
> kalman=# create table test ( a integer, b integer );
> CREATE TABLE
> kalman=# create table test1 ( c integer , d test );
> CREATE TABLE

> kalman=# alter table test drop column b;
> ALTER TABLE <--- Here I think the server shall complain about

Yeah, the design intention is that the ALTER should refuse to do it.
Looks like I missed a case. Will fix, thanks for the report.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2004-07-26 06:12:00 Re: PG 7.4.3 optimizer choosing sequential scan. Why?
Previous Message Christopher Kings-Lynne 2004-07-26 05:26:37 Weird...but correct?