Re: Hot standby and removing VACUUM FULL
От | Heikki Linnakangas |
---|---|
Тема | Re: Hot standby and removing VACUUM FULL |
Дата | |
Msg-id | 4B0854D0.9020502@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: Hot standby and removing VACUUM FULL (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Hot standby and removing VACUUM FULL
|
Список | pgsql-hackers |
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. > (Do we have a list of open issues somewhere, so that this > won't get forgotten?) I'm keeping one as I bump into things. I'll post it again soon. Actually, I should probably put it on the wiki. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: