From: | <furuyao(at)pm(dot)nttdata(dot)co(dot)jp> |
---|---|
To: | <masao(dot)fujii(at)gmail(dot)com> |
Cc: | <sawada(dot)mshk(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, <teranishih(at)nttdata(dot)co(dot)jp> |
Subject: | Re: pg_receivexlog --status-interval add fsync feedback |
Date: | 2014-09-05 05:51:27 |
Message-ID: | A9C510524E235E44AE909CD4027AE196BF7C70D1D3@MBX-MSG-SV03.msg.nttdata.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > Thanks for the review!
> >
> > I understand the attention message wasn't appropriate.
> >
> > To report the write location, even If you do not specify a replication
> slot.
> > So the fix only appended messages.
> >
> > There was a description of the flush location section of '-S' option,
> > but I intended to catch eye more and added a message.
> >
> > Is it better to make specification of the -S option indispensable?
>
> The patch cannot be applied to HEAD cleanly. Could you update the patch?
Thank you for pointing out.
Updated the patch.
Regards,
--
Furuya Osamu
Attachment | Content-Type | Size |
---|---|---|
pg_receivexlog-fsync-feedback-v5.patch | application/octet-stream | 9.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Vladimir Romanov | 2014-09-05 05:54:14 | ODBC Driver performance comparison |
Previous Message | Laurence Rowe | 2014-09-05 04:21:26 | Re: A mechanism securing web applications in DBMS |