| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | detailed error message of pg_waldump |
| Date: | 2021-06-04 08:35:33 |
| Message-ID: | 20210604.173533.349866689278295774.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
In a very common operation of accidentally specifying a recycled
segment, pg_waldump often returns the following obscure message.
$ pg_waldump 00000001000000000000002D
pg_waldump: fatal: could not find a valid record after 0/2D000000
The more detailed message is generated internally and we can use it.
That looks like the following.
$ pg_waldump 00000001000000000000002D
pg_waldump: fatal: unexpected pageaddr 0/24000000 in log segment 00000001000000000000002D, offset 0
Is it work doing?
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| Attachment | Content-Type | Size |
|---|---|---|
| pg_waldump_detailed_error.patch | text/x-patch | 3.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2021-06-04 08:43:46 | Re: Transactions involving multiple postgres foreign servers, take 2 |
| Previous Message | Andrey Lepikhov | 2021-06-04 08:26:29 | Fast COPY FROM based on batch insert |