Let me see, for example one insert type (inser into table2 (select * from table1), where table have size 26megas,make 226megas for archives files.
(i made a test with parameter wal_bufffer before this is defaul value 64k and the same commando make 640megas of archives after modify to 1024k a take 226m)
however continuous confused for me.
how 26mega of insert generate 226mega of archive.
(i made a test with parameter wal_bufffer before this is defaul value 64k and the same commando make 640megas of archives after modify to 1024k a take 226m)
however continuous confused for me.
how 26mega of insert generate 226mega of archive.
mDe: Craig Ringer <craig@xxxxxxxxxxxxxxxxxxxxx>
Para: paulo matadr <saddoness@xxxxxxxxxxxx>
Cc: GENERAL <pgsql-general@xxxxxxxxxxxxxx>
Enviadas: Sexta-feira, 14 de Novembro de 2008 6:25:11
Assunto: Re: Archive files growth!!!
paulo matadr wrote:
> How the best way to controling fast growth in my Database.
I'm going to assume, based on the config info you quoted and the subject line, that you mean controlling the size of the archived WAL files on the warm standby server. If that assumption is incorrect, you might want to reply with a bit more detail about your problem.
If so, one option may be to use pg_clearxlogtail to zero the unused portions of the backup copies of your WAL files then compress them with (eg) gzip. Make sure to TEST YOUR BACKUPS.
--
Craig Ringer
-- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Novos endereços, o Yahoo! que você conhece. Crie um email novo com a sua cara @ymail.com ou @rocketmail.com.
