From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Kovacs Zoltan" <kovacsz(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <jm(dot)poure(at)freesurf(dot)fr>, "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, <dpage(at)pgadmin(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: alter table drop column status |
Date: | 2002-02-20 02:41:32 |
Message-ID: | GNELIHDDFBOCMGBFGEFOEEHJCBAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Zoltan,
I'd love to see a pl/pgsql funciton to drop a column submitted to the list.
I'll submit a set null / set not null one and maybe we can make up a little
package of functions for techdocs.postgres.org.
In fact, getting these pl/pgsql functions right will make it easier to write
C versions, which might make it easier to integrate the functionality
directly into postgres...
Chris
> -----Original Message-----
> From: Kovacs Zoltan [mailto:kovacsz(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu]
> Sent: Wednesday, 20 February 2002 2:07 AM
> To: Tom Lane
> Cc: Christopher Kings-Lynne; jm(dot)poure(at)freesurf(dot)fr; Hiroshi Inoue;
> dpage(at)pgadmin(dot)org; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] alter table drop column status
>
>
> > > I'm afraid LOCK is not available inside a PLPGSQL function
> >
> > Works fine for me ...
>
> Hmm, it works for me, too. OK, I see no more rocks ahead writing a PLPGSQL
> function which drops a column. It'll be slow, but it'll work. However, a C
> function would be better. Unfortunately I have no experience in writing
> libpq or ecpg functions. Is it a problem for you if I contribute a PLPGSQL
> code?
>
> Regards, Zoltan
>
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2002-02-20 02:53:57 | Re: pg_dump: use ALTER TABLE for PKs |
Previous Message | Tatsuo Ishii | 2002-02-20 00:50:55 | Re: UTF-8 data migration problem in Postgresql 7.2 |