Search Postgresql Archives

Re: Long running update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Andrew Janian" <ajanian@xxxxxxxxxxxxx> writes:
> I needed to expand the size of one of the varchar columns in a table of
> my 135GB database.

How big is the particular table you are doing this on?  What foreign key
relationships is it involved in?  (I wonder if the time is going into FK
checking more than the actual update...)  What PG version exactly?

Personally, at this point I'd cancel the update while there's still time
to do a VACUUM before you have to be operational again.  You could do
the required operation (increasing a varchar's limit) in O(1) time by
twiddling the system catalogs.  You're going to need a VACUUM anyway
because of all the dead tuple versions left behind by the UPDATE.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux