Re: BETWEEN Node & DROP COLUMN

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: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BETWEEN Node & DROP COLUMN
Date: 2002-07-04 06:00:05
Message-ID: 200207040600.g64605E03440@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> No, he only breaks even for client cleanliness --- either approach
> >> *will* require changes in clients that look at pg_attribute.
>
> > Uh, Christopher already indicated three clients, psql, pg_dump, and
> > another that will not require changes for Hiroshi's approach, but will
> > require changes for isdropped.
>
> Oh? If either psql or pg_dump don't break, it's a mere coincidence,
> because they certainly depend on attnum. (It's also pretty much
> irrelevant considering they're both under our control and hence easily
> fixed.)
>
> I'm fairly certain that Christopher is mistaken, anyhow. Check the
> manipulations of attribute defaults for a counterexample in pg_dump.

Well, it seems isdropped is going to have to be checked by _any_ client,
while holes in the number will have to be checked by _some_ clients. Is
that accurate?

--
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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-07-04 06:02:31 Re: BETWEEN Node & DROP COLUMN
Previous Message Hiroshi Inoue 2002-07-04 05:53:55 Re: BETWEEN Node & DROP COLUMN