Re: Hot standby and removing VACUUM FULL - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Hot standby and removing VACUUM FULL
Date
Msg-id 4B0854D0.9020502@enterprisedb.com
Whole thread Raw
In response to Re: Hot standby and removing VACUUM FULL  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Hot standby and removing VACUUM FULL
List 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 by date:

Previous
From: Mark Richardson
Date:
Subject: Re: [INTERFACES] ecpg & 8.3 -> 8.4 migration
Next
From: "Florian G. Pflug"
Date:
Subject: Re: DEFAULT of domain ignored in plpgsql (8.4.1)