Re: pg_get_triggerdef in pg_dump
| От | Alvaro Herrera |
|---|---|
| Тема | Re: pg_get_triggerdef in pg_dump |
| Дата | |
| Msg-id | 20030618143537.GB2460@dcc.uchile.cl обсуждение исходный текст |
| Ответ на | Re: pg_get_triggerdef in pg_dump (Andreas Pflug <Andreas.Pflug@web.de>) |
| Ответы |
Re: pg_get_triggerdef in pg_dump
|
| Список | pgsql-hackers |
On Wed, Jun 18, 2003 at 12:59:36PM +0200, Andreas Pflug wrote:
> What I need again and again, is changing the size of a column (rarely
> the type). For pgsql, I'd have to drop the column, and need to recreate
> all views. For MSSQL, it won't matter if the column is dropped/recreated
> or just resized, the view won't notice until it's used again.
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.
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Porque Kim no hacia nada, pero, eso si,
con extraordinario exito" ("Kim", Kipling)
В списке pgsql-hackers по дате отправления: