From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Andres Freund <andres(at)anarazel(dot)de> |
Subject: | error context for vacuum to include block number |
Date: | 2019-11-20 21:06:00 |
Message-ID: | 20191120210600.GC30362@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Aug 07, 2019 at 04:51:54PM -0700, Andres Freund wrote:
https://www.postgresql.org/message-id/20190807235154.erbmr4o4bo6vgnjv%40alap3.anarazel.de
| Ugh :(
|
| We really need to add a error context to vacuumlazy that shows which
| block is being processed.
I eeked out a minimal patch.
I renamed "StringInfoData buf", since it wasn't nice to mask it by
"Buffer buf".
postgres=# SET statement_timeout=99;vacuum t;
SET
2019-11-20 14:52:49.521 CST [6319] ERROR: canceling statement due to statement timeout
2019-11-20 14:52:49.521 CST [6319] CONTEXT: block 596
2019-11-20 14:52:49.521 CST [6319] STATEMENT: vacuum t;
Justin
Attachment | Content-Type | Size |
---|---|---|
v1-0001-vacuum-errcontext-to-show-block-being-processed.patch | text/x-diff | 4.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2019-11-20 21:19:32 | Re: add a MAC check for TRUNCATE |
Previous Message | Thomas Munro | 2019-11-20 20:40:02 | Re: TAP tests aren't using the magic words for Windows file access |