On Tue, Oct 26, 2010 at 11:10 PM, Divakar Singh <dpsmails@xxxxxxxxx> wrote: > Dear All, > Thanks for your inputs on the insert performance part. > Any suggestion on storage requirement? > VACUUM is certainly not an option, because this is something related to > maintenance AFTER insertion. > I am talking about the plain storage requirement w.r. to Oracle, which I > observed is twice of Oracle in case millions of rows are inserted. > Anybody who tried to analyze the average storage requirement of PG w.r. to > Oracle? There isn't much you can to about storage use other than avoid stupid things (like using char() vs varchar()), smart table layout, toast compression, etc. Are you sure this is a problem? merlin -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
