From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: error context for vacuum to include block number |
Date: | 2020-01-20 05:41:59 |
Message-ID: | 20200120054159.GT26045@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Rebased against 40d964ec997f64227bc0ff5e058dc4a5770a70a9
I moved some unrelated patches to a separate thread ("vacuum verbose detail logs are unclear")
Attachment | Content-Type | Size |
---|---|---|
v9-0001-dedup2-skip_blocks.patch | text/x-diff | 9.1 KB |
v9-0002-vacuum-errcontext-to-show-block-being-processed.patch | text/x-diff | 3.8 KB |
v9-0003-add-errcontext-callback-in-lazy_vacuum_heap-too.patch | text/x-diff | 1.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Paul A Jungwirth | 2020-01-20 05:57:57 | Re: range_agg |
Previous Message | Justin Pryzby | 2020-01-20 05:30:14 | Re: doc: vacuum full, fillfactor, and "extra space" |