| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | mahendrakar s <mahendrakarforpg(at)gmail(dot)com>, SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_receivewal fail to streams when the partial file to write is not fully initialized present in the wal receiver directory |
| Date: | 2022-09-22 04:37:01 |
| Message-ID: | YyvmbSGXIcoPbQNA@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 22, 2022 at 07:16:41AM +0530, Bharath Rupireddy wrote:
> t/010_pg_basebackup.pl ... 134/?
> # Failed test 'pg_basebackup reports checksum mismatch stderr
> /(?^s:^WARNING.*checksum verification failed)/'
> # at t/010_pg_basebackup.pl line 769.
> # 'unrecognized win32 error code: 123WARNING:
> checksum verification failed in file "./base/5/16399", block 0:
> calculated 4C09 but expected B3F6
> # pg_basebackup: error: checksum error occurred
Shouldn't we extend the mapping table in win32error.c so as the
information provided is more useful when seeing this error, then?
There could be other code path able to trigger this failure, or other
hackers working on separate features that could benefit from this
extra information.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2022-09-22 04:46:24 | Re: [PoC] Improve dead tuple storage for lazy vacuum |
| Previous Message | Michael Paquier | 2022-09-22 04:34:04 | Re: pg_basebackup's --gzip switch misbehaves |