Re: pg_get_triggerdef in pg_dump - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: pg_get_triggerdef in pg_dump
Date
Msg-id 01f801c33601$31457a90$6500a8c0@fhp.internal
Whole thread Raw
In response to Re: pg_get_triggerdef in pg_dump  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: pg_get_triggerdef in pg_dump
List 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



pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: pg_get_triggerdef in pg_dump
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Re: pg_get_triggerdef in pg_dump