Re: [SQL] VACUUM FULL vs dump & restore

2005-09-24 Thread Aldor
Another way how to do it with having access to the data in the same time is to create a new table, named a little bit differently and do an: insert into [table]2 select * from[table]; Then switch to the second table. Then you have to do on the first table the TRUNCATE and DROP. For getti

Re: [SQL] VACUUM FULL vs dump & restore

2005-09-24 Thread Aldor
Hello Ilya, you have to check for yourself which method is faster - just test it with a stopwatch;-) You have to take care, because when you make VACUUM FULL, then it vacuums also the system tables, etc. of postgres. I'm not sure if this is the same way VACUUM goes through all objects, but I'd m

[SQL] VACUUM FULL vs dump & restore

2005-09-23 Thread Ilya A. Kovalenko
Greetings, What advantages I lose, when using dump-truncate-restore (table or whole DB) instead of performing VACUUM FULL ? In both cases I have no access to data, but first is much faster (by subjective estimate). Thank you, Ilya A. Kovalenko (mailto:[EMAIL PROTECTED])