On Tue, Mar 13, 2012 at 5:14 AM, Vick Khera <vivek@xxxxxxxxx> wrote: > I'll bet what happened was postgres re-wrote your table for you, > effectively doing a compaction. You can get similar effect by doing > an alter table and "changing" an INTEGER field to be INTEGER. > Postgres does not optimize that do a no-op, so you get the re-writing > effect. How does table rewriting work? Does it happen a row at a time or all at once? In other words, how much free disk space is needed on an 800 TB filesystem to rewrite a 550 TB table? (Have I got enough space?) Aleksey -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
