Re: pg_get_triggerdef in pg_dump

Поиск
Список
Период
Сортировка
От Christopher Kings-Lynne
Тема Re: pg_get_triggerdef in pg_dump
Дата
Msg-id 01dc01c33600$bfae31b0$6500a8c0@fhp.internal
обсуждение исходный текст
Ответ на Re: pg_get_triggerdef in pg_dump  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Список pgsql-hackers
> If that's what you need you can always change the system catalogs
> manually.  For CHAR(n) and VARCHAR(n) you change pg_attribute.atttypmod
> to (n+4).  For NUMERIC(n,m) it's something like (n<<16) + m + 4 or maybe
> (m<<16) + n + 4, don't remember right now.
>
> Be sure to check that your data is in a safe place before you do this,
> and double check before you commit the transaction if you do it
> manually.

Is there demand for an ALTER COLUMN/SET TYPE that is restricted to binary
compatible casts and increasing length changes?

Chris



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andreas Pflug
Дата:
Сообщение: Re: allowed user/db variables
Следующее
От: "Christopher Kings-Lynne"
Дата:
Сообщение: Re: pg_get_triggerdef in pg_dump