Re: [COMMITTERS] pgsql: Fix VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Fix VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL
Date: 2016-09-07 12:47:08
Message-ID: CAHGQGwEiHmNeBUtGizLj3edV7=1dcLYj6cjr2PW+r5PwCxxXdQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Sep 6, 2016 at 11:41 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Fix VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL
>
> lazy_truncate_heap() was waiting for
> VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL, but in microseconds
> not milliseconds as originally intended.

Don't we need to back-patch this?

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2016-09-07 12:50:49 Re: [COMMITTERS] pgsql: Fix VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL
Previous Message Tom Lane 2016-09-07 03:56:06 pgsql: Add a HINT for client-vs-server COPY failure cases.

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2016-09-07 12:50:49 Re: [COMMITTERS] pgsql: Fix VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL
Previous Message Simon Riggs 2016-09-07 12:45:50 Re: Vacuum: allow usage of more than 1GB of work mem