Re: hot standby documentation

On Tue, Jun 22, 2010 at 8:56 AM, Joshua Tolley <eggyknap(at)gmail(dot)com> wrote:
> I'm not sure it's worth pointing out that the database might still use temp
> files. It seems an unnecessary level of detail. I realize you're probably
> putting it here because you've edited that bit out of the docs elsewhere, but
> I still think it's unnecessary detail. That said, if it has to go somewhere,
> +1 for this change.

I agree, and your guess about how it ended up there is correct. Removed.

>> -    Queries executed on the standby will be correct with regard to the transactions
>> -    that had been recovered at the start of the query, or start of first statement
>> -    in the case of serializable transactions. In comparison with the primary,
>> -    the standby returns query results that could have been obtained on the primary
>> -    at some moment in the past.
>> +    Queries executed on the standby will see a view of the database that
>> +    existed on the master at some moment in the past.
>
> Is it really that non-deterministic? /me admits not having followed that
> discussion. Although the original version is pretty complex, it gives the user
> some feel for the particular moment in the past that their snapshot will
> represent. If the original is incorrect, it would be nice to replace it with
> something that doesn't suggest the user might end up with a snapshot from last
> week.

I had another go at this.

> s/is depending/depends/

Fixed. See attached.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company