Re: pg_basebackup check vs Windows file path limits - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pg_basebackup check vs Windows file path limits
Date
Msg-id 202311111631.uuwr4gehzwti@alvherre.pgsql
Whole thread Raw
In response to Re: pg_basebackup check vs Windows file path limits  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pg_basebackup check vs Windows file path limits  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On 2023-Jul-08, Andrew Dunstan wrote:

> # Running: pg_basebackup -D
C:\\tools\\nmsys64\\home\\pgrunner\\bf\\root\\REL_16_STABLE\\pgsql.build/testrun/pg_basebackup/010_pg_basebackup/data/t_010_pg_basebackup_main_data/backup/tarbackup2
-hC:/tools/nmsys64/tmp/63ohSgsh21 -p 54699 --checkpoint fast --no-sync -Ft
 
> WARNING:  aborting backup due to backend exiting before pg_backup_stop was called
> pg_basebackup: error: could not initiate base backup: ERROR:  could not get junction for "./pg_replslot": More data
isavailable.
 

Why not patch pgreadlink to use the method recommended by Microsoft,
that DeviceIoControl() is called first with a NULL reparseBuffer to
determine the size needed, then a second time with a buffer of that
size?

https://learn.microsoft.com/en-us/windows/win32/api/ioapiset/nf-ioapiset-deviceiocontrol

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Vladimir Churyukin
Date:
Subject: Re: Making auto_explain more useful / convenient
Next
From: Alexander Lakhin
Date:
Subject: Re: pg_basebackup check vs Windows file path limits