Re: [COMMITTERS] pgsql: Fix VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL
| От | Tom Lane |
|---|---|
| Тема | Re: [COMMITTERS] pgsql: Fix VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL |
| Дата | |
| Msg-id | 1670.1473256696@sss.pgh.pa.us обсуждение |
| Ответ на | Re: [COMMITTERS] pgsql: Fix VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL (Simon Riggs <simon@2ndquadrant.com>) |
| Ответы |
Re: [COMMITTERS] pgsql: Fix VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL
|
| Список | pgsql-hackers |
Simon Riggs <simon@2ndquadrant.com> writes:
> On 7 September 2016 at 13:47, Fujii Masao <masao.fujii@gmail.com> wrote:
>> On Tue, Sep 6, 2016 at 11:41 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>>> 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?
> If we do then a database-wide VACUUM on a busy database will take
> substantially longer than it does now.
On the other hand, it's also more likely to successfully perform desired
truncations.
> That may not be perceived as a "fix" by everybody, so we should not do
> it without an explicit agreement by many.
Agreed, but I vote with Fujii-san for back-patching.
regards, tom lane
В списке pgsql-hackers по дате отправления: