Re: Altering a column type - Most efficient way

Поиск
Список
Период
Сортировка
Искать
От
Ow Mun Heng
Тема
Re: Altering a column type - Most efficient way
Дата
Msg-id
1215742620.853.10.camel@neuromancer.home.net
Ответ на
Список
Дерево обсуждения
Altering a column type - Most efficient way Ow Mun Heng <Ow.Mun.Heng@wdc.com>
Re: Altering a column type - Most efficient way Mario Weilguni <mweilguni@sime.com>
Re: Altering a column type - Most efficient way Ow Mun Heng <Ow.Mun.Heng@wdc.com>
Re: Altering a column type - Most efficient way Alvaro Herrera <alvherre@commandprompt.com>
Re: Altering a column type - Most efficient way Ow Mun Heng <Ow.Mun.Heng@wdc.com>
Re: Altering a column type - Most efficient way Alvaro Herrera <alvherre@commandprompt.com>
Re: Altering a column type - Most efficient way Tom Lane <tgl@sss.pgh.pa.us>
Re: Altering a column type - Most efficient way "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
[SOLVED] Re: Altering a column type - Most efficient way Ow Mun Heng <Ow.Mun.Heng@wdc.com>
Re: Altering a column type - Most efficient way Mario Weilguni <mweilguni@sime.com>
On Thu, 2008-07-10 at 09:57 -0400, Alvaro Herrera wrote:
> Ow Mun Heng wrote:
> 
> > This is what I see on the table
> > 
> > NEW attypmod = -1
> > OLD attypmod =  8
> 
> 8 means varchar(4) which is what you said you had (4+4)
> -1 means unlimited size.
> 

This is cool. 

If it were this simple a change, I'm not certain why (I believe) PG is
checking each and every row to see if it will fit into the new column
definition/type. 

Thus, I'm still a bit hesitant to do the change, although it is
definitely a very enticing thing to do. ( I presume also that this
change will be instantaneous and does not need to check on each and
every row of the table?)

Thanks./
В списке pgsql-performance по дате отправления
От: Scott Marlowe
Дата:
От: Ramasubramanian
Дата:
Сообщение: Trigger is taking time to fire
FAQ