From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Add hash index caution to CREATE INDEX docs |
Date: | 2012-10-17 08:04:29 |
Message-ID: | CAA-aLv4vm=pP_ct9hx5V3HPcrNKZE7wXJNo1ui4yaTT-QkwWNQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On 17 October 2012 09:02, Thom Brown <thom(at)linux(dot)com> wrote:
> On 17 October 2012 08:37, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> Add hash index caution to CREATE INDEX docs
>>
>> Branch
>> ------
>> REL8_3_STABLE
>>
>> Details
>> -------
>> http://git.postgresql.org/pg/commitdiff/6166c7301ed9286c1e2af2f83a39e8b8225338bf
>>
>> Modified Files
>> --------------
>> doc/src/sgml/ref/create_index.sgml | 12 ++++++++++++
>> 1 files changed, 12 insertions(+), 0 deletions(-)
>
> s/anwers/answers/
>
> Also, you've said that hash indexes aren't replicated using warm
> standby, which may suggest you can replicate using hot standby, which
> you can't. Shouldn't we say that they remain static on a standby
> after a base backup, and that replication doesn't currently include
> hash indexes?
Apologies, I see that you committed this is 2 steps, so the hot
standby remark doesn't stand for these versions. The typo, however,
applies to both sets of commits. ;)
--
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2012-10-17 08:20:18 | pgsql: Fix typo in previous commit |
Previous Message | Thom Brown | 2012-10-17 08:02:40 | Re: pgsql: Add hash index caution to CREATE INDEX docs |