On 2020/02/17 17:52, Fujii Masao wrote:
On 2020/02/17 14:28, Kasahara Tatsuhito wrote:
Hi,
On Mon, Feb 17, 2020 at 1:07 PM Masahiko Sawada
wrote:
For the patch, we can put also the declaration of ru0 into the loop.
Thanks for your reply.
Hmm, certainly that it may be better.
Fix the v2
On 2020/02/17 14:28, Kasahara Tatsuhito wrote:
Hi,
On Mon, Feb 17, 2020 at 1:07 PM Masahiko Sawada
wrote:
For the patch, we can put also the declaration of ru0 into the loop.
Thanks for your reply.
Hmm, certainly that it may be better.
Fix the v2 patch and attached.
Thanks for updating
Hi,
On Mon, Feb 17, 2020 at 1:07 PM Masahiko Sawada
wrote:
> For the patch, we can put also the declaration of ru0 into the loop.
Thanks for your reply.
Hmm, certainly that it may be better.
Fix the v2 patch and attached.
Best regards,
--
Tatsuhito Kasahara
kasahara.tatsuhito _at_ gmail.com
On Mon, 17 Feb 2020 at 12:44, Kasahara Tatsuhito
wrote:
>
> Hi,
>
> On Fri, Feb 14, 2020 at 4:50 PM Fujii Masao wrote:
> > Regarding the patch, isn't it better to put pg_rusage_init() at the
> > top of do loop block? If we do this, as a side-effect, we can get
> > rid of pg_rusage_init() at the t
Hi,
On Fri, Feb 14, 2020 at 4:50 PM Fujii Masao wrote:
> Regarding the patch, isn't it better to put pg_rusage_init() at the
> top of do loop block? If we do this, as a side-effect, we can get
> rid of pg_rusage_init() at the top of lazy_truncate_heap().
Thanks for your reply.
Yeah, it makes sens
On Tue, Aug 13, 2019 at 1:16 PM Kasahara Tatsuhito
wrote:
>
> Hi,
>
> I got following log messages when measured the heap truncating
> duration in a vacuum.
>
> =
> INFO: "dst": suspending truncate due to conflicting lock request
> INFO: "dst":
Hi,
I got following log messages when measured the heap truncating
duration in a vacuum.
=
INFO: "dst": suspending truncate due to conflicting lock request
INFO: "dst": truncated 550073 to 101472 pages
DETAIL: CPU: user: 0.35 s, system: 4.92
