From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Hannu Krosing" <hannu(at)tm(dot)ee>, "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New manual chapters |
Date: | 2002-08-06 06:02:53 |
Message-ID: | GNELIHDDFBOCMGBFGEFOCEIJCDAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> But we *have* drop column.
I know that....I think I must have been on crazy pills when I mentioned it
in regards to DROP COLUMN...
> If we don't do attlognum for 7.3, there's little point in doing it at
> all. By the time 7.4 comes out, clients that formerly expected a
> consecutive series of attnums will have found some way to cope.
I think that what Hannu is saying is that if we implemented changing column
type with a drop and an add, all queries that used to go 'select * from'
would return the modified column at the end of the list of columns instead
of in its original position.
> I'm not sure that I feel any strong sense of urgency about this ---
> 7.3 will break clients that examine the system catalogs in many ways,
> and this doesn't seem like the nastiest of 'em.
>
> I just wanted to point out that "we'll do it later" isn't a profitable
> attitude towards attlognum. Either it's done by the end of August,
> or it never gets done at all.
Ok - don't know if I'll be able to tho.
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-08-06 06:10:25 | Re: FUNC_MAX_ARGS benchmarks |
Previous Message | lockhart | 2002-08-06 05:57:23 | From GROUPE BULL. |