Re: pg_get_triggerdef in pg_dump
| От | Christopher Kings-Lynne |
|---|---|
| Тема | Re: pg_get_triggerdef in pg_dump |
| Дата | |
| Msg-id | 01f801c33601$31457a90$6500a8c0@fhp.internal обсуждение исходный текст |
| Ответ на | Re: pg_get_triggerdef in pg_dump (Christopher Kings-Lynne <chriskl@familyhealth.com.au>) |
| Ответы |
Re: pg_get_triggerdef in pg_dump
|
| Список | 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 по дате отправления: