On Jun 8, 1:46 am, [EMAIL PROTECTED] (Andrew Sullivan) wrote: > On Thu, Jun 07, 2007 at 12:07:03AM -0700, Charles.Hou wrote: > > i use the VACUUM VERBOSE a table , but it had been hold 10 minutes . i > > must use the linux command " kill " to exit the VACUUM. > > after i kill this PID, the PostgreSql have been restart > > automatically. > > Maybe it was doing work. Why did you kill it? If there is a problem > on that table, I wouldn't be surprised that it'd take 10 minutes. > You just caused all the work it started to do to be undone, and to > cause more bloat. But. . . > > > DETAIL: 0 dead row versions cannot be removed yet. > > . . . this suggests you don't have bloat on that table at least. So > it sounds to me like your disk use is going up because you have a lot > of data. > > A > > -- > Andrew Sullivan | [EMAIL PROTECTED] > In the future this spectacle of the middle classes shocking the avant- > garde will probably become the textbook definition of Postmodernism. > --Brad Holland > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly
i have traced the size of the table. About 1000 new rows will be inserted into the table in one day. each row has 300 bytes. 1000*300/1024=293K, but the size of this table had been increased 3MB. 3MB-293K=2.7MB...Why?where is the 2.7MB? ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match