| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL |
| Date: | 2016-09-06 14:41:26 |
| Message-ID: | E1bhHZ0-0003Yx-Us@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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.
Found by code inspection.
Simon Riggs
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/dcb12ce8d8691e0e526d3f38d14c4d7fc9c664f5
Modified Files
--------------
src/backend/commands/vacuumlazy.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2016-09-06 16:19:31 | Re: [COMMITTERS] pgsql: Make initdb's suggested "pg_ctl start" command line more reliabl |
| Previous Message | Michael Paquier | 2016-09-06 12:36:49 | Re: pgsql: Add putenv support for msvcrt from Visual Studio 2013 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anastasia Lubennikova | 2016-09-06 15:09:40 | Re: Refactoring of heapam code. |
| Previous Message | Jeevan Chalke | 2016-09-06 14:22:22 | Re: PassDownLimitBound for ForeignScan/CustomScan |