| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>, "Alvaro Herrera" <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_get_triggerdef in pg_dump |
| Date: | 2003-06-19 01:22:03 |
| Message-ID: | 01f801c33601$31457a90$6500a8c0@fhp.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Hm, you're right, 'thou I wouldn't recommend this to the average user,
> and wonder if this will be possible for all future pgsql versions too.
> I'm considering adding safe support for this type of column change to
> pgAdmin3.
> There might be other cases of legal direct change of system catalog
> entries, e,g. varchar to text, if they all are only names for internally
> identical data structures. Can you tell which datatypes may be legally
> interchanged?
Yes, you can check if they're binary compatible from the pg_cast table....
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-06-19 01:23:49 | Re: pg_get_triggerdef in pg_dump |
| Previous Message | Christopher Kings-Lynne | 2003-06-19 01:18:50 | Re: pg_get_triggerdef in pg_dump |