Re: More efficient DELETE ... ?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-sql(at)postgreSQL(dot)org
Subject: Re: More efficient DELETE ... ?
Date: 2000-09-30 02:24:37
Message-ID: 200009300224.WAA02433@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Just a reminder that this is taken care of. It only WARNs in cases
where we suspect they really made a mistake.

test=> select * from pg_class s where pg_class.oid =34;
NOTICE: Adding missing FROM-clause entry for table pg_class

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > In fact, someone can just remove the #ifdef WARN_FROM defines around the
> > code and regenerate the regression tests and all will stay in sync.
>
> IIRC, Thomas felt that his outer join changes were going to break those
> warnings anyway --- that's why we had them commented out. No point in
> trying to turn them on until the outer-join dust settles.
>
> regards, tom lane
>
> ************
>
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Keith Wong 2000-09-30 02:32:13 Transaction isolation level for plpgsql
Previous Message Joel Mc Graw 2000-09-29 23:20:34 Re: invoke an external shell script from a function