From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Add flag values in WAL description to all heap records |
Date: | 2018-11-14 14:02:46 |
Message-ID: | 20181114140246.67q6tmhedwlo6v3p@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 2018-Nov-14, Michael Paquier wrote:
> Add flag values in WAL description to all heap records
>
> Hexadecimal is consistently used as format to not bloat too much the
> output but keep it readable. This information is useful mainly for
> debugging purposes with for example pg_waldump.
Just noticed: ISTM we should also print the infobits_set flags in
xl_heap_lock and xl_heap_lock_updated. I can add those.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-11-14 16:10:30 | pgsql: Lower lock level for renaming indexes |
Previous Message | Michael Paquier | 2018-11-14 07:50:10 | pgsql: Initialize TransactionState and user ID consistently at transact |
From | Date | Subject | |
---|---|---|---|
Next Message | Ronan Dunklau | 2018-11-14 14:43:33 | Parametrization and UNION in view |
Previous Message | Darafei Komяpa Praliaskouski | 2018-11-14 13:59:02 | Re: Changing SQL Inlining Behaviour (or...?) |