| From: | KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, Florian Weimer <fweimer(at)redhat(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logging WAL when updating hintbit |
| Date: | 2013-11-19 06:54:03 |
| Message-ID: | 528B0B0B.4060009@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
(2013/11/15 19:27), Sawada Masahiko wrote:
> On Thu, Nov 14, 2013 at 7:51 PM, Florian Weimer <fweimer(at)redhat(dot)com> wrote:
>> On 11/14/2013 07:02 AM, Sawada Masahiko wrote:
>>
>>> I attached patch adds new wal_level 'all'.
>>
>>
>> Shouldn't this be a separate setting? It's useful for storage which
>> requires rewriting a partially written sector before it can be read again.
>>
>
> Thank you for comment.
> Actually, I had thought to add separate parameter.
I think that he said that if you can proof that amount of WAL is almost same and
without less performance same as before, you might not need to separate
parameter in your patch.
Did you test about amount of WAL size in your patch?
I'd like to know it.
Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maxim Boguk | 2013-11-19 07:03:26 | Large offset optimization and index only scan |
| Previous Message | Tom Lane | 2013-11-19 06:31:51 | Re: lock on object is already held |