Re: Hot standby and removing VACUUM FULL
От | Simon Riggs |
---|---|
Тема | Re: Hot standby and removing VACUUM FULL |
Дата | |
Msg-id | 1259112249.27757.11157.camel@ebony обсуждение исходный текст |
Ответ на | Re: Hot standby and removing VACUUM FULL (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: Hot standby and removing VACUUM FULL
|
Список | pgsql-hackers |
On Sat, 2009-11-21 at 23:00 +0200, Heikki Linnakangas wrote: > Tom Lane wrote: > > Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes: > >> Tom Lane wrote: > >>> There's no equivalent of XLogArchivingActive()? > > > >> XLogArchivingMode() == false enables us to skip WAL-logging in > >> operations like CLUSTER or COPY, which is a big optimization. I don't > >> see anything like that in Hot Standby. There is a few small things that > >> could be skipped, but nothing noticeable. > > > > Huh? Surely HS requires XLogArchivingMode as a prerequisite ... > > Oh, sure! But there's no switch that needs to be enabled in the master > in addition to that. We've tried hard to have it "just work". But I wonder whether we should have a parameter to allow performance testing on the master? If nobody finds any issues then we can remove it again, or at least make it a hidden developer option. -- Simon Riggs www.2ndQuadrant.com
В списке pgsql-hackers по дате отправления: