| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: pgsql: Add new pg_walsummary tool. |
| Date: | 2024-01-11 18:49:12 |
| Message-ID: | CA+TgmoYuShd8xDsR=G1ZhRcT3gOkWn0ZmqsR7Oz+gvhxJreTaQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Thu, Jan 11, 2024 at 12:56 PM Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> Add new pg_walsummary tool.
culicidae is unhappy with this, but I don't yet understand why. The output is:
# Failed test 'stdout shows block 0 modified'
# at t/002_blocks.pl line 85.
# 'TS 1663, DB 5, REL 16384, FORK main: blocks 0..1'
# doesn't match '(?^m:FORK main: block 0$)'
The test is expecting block 0 to be modified, but block 1 to be
unmodified, but here, both blocks are modified. That would maybe make
sense if this machine had a really big block size, but that doesn't
seem to be the case. Or, maybe the test has erred in failing to
disable autovacuum -- though it does take other precautions to try to
prevent that from interfering.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-01-11 18:58:18 | Re: pgsql: Add new pg_walsummary tool. |
| Previous Message | Robert Haas | 2024-01-11 18:43:02 | pgsql: Remove hastup from LVPagePruneState. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-01-11 18:58:18 | Re: pgsql: Add new pg_walsummary tool. |
| Previous Message | Robert Haas | 2024-01-11 18:43:27 | Re: Emit fewer vacuum records by reaping removable tuples during pruning |