| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: AW: AW: AW: ALTER TABLE DROP COLUMN |
| Date: | 2000-10-14 02:50:56 |
| Message-ID: | Pine.BSF.4.21.0010132350050.654-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 13 Oct 2000, Tom Lane wrote:
> The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> > okay, but, again based on my impression of what Tom has stated, and
> > previous conversations on this topic, the key problem is what happens if I
> > drop a column and a later date decide add a new column of the same name,
> > what happens?
>
> I'm not very worried about that --- presumably the old column is either
> marked as dead or gone entirely from pg_attribute, so why should there
> be any confusion?
right, but, if you add a column after it was previuosly marked dead, does
it then create a second column in pg_attribute with that same
name? *raised eyebrow*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-10-14 02:53:28 | Re: Re: [HACKERS] My new job |
| Previous Message | Tom Lane | 2000-10-14 02:40:16 | Re: AW: AW: AW: ALTER TABLE DROP COLUMN |