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 202311151134.774tav746obb@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
List pgsql-hackers
On 2023-Nov-13, Andrew Dunstan wrote:

> > size?
> > 
> > https://learn.microsoft.com/en-us/windows/win32/api/ioapiset/nf-ioapiset-deviceiocontrol
> 
> Hmm, here's what that page says - I can't see it saying what you're
> suggesting here - am I missing something?:

I don't think so.  I think I just confused myself.  Reading the docs it
appears that other Windows APIs work as I described, but not this one.

Anyway, after looking at it a bit more, I realized that this code uses
MAX_PATH as basis for its buffer's length limit -- and apparently on
Windows that's only 260, much shorter than MAXPGPATH (1024) which our
own code uses to limit the buffers given to readlink().  So maybe fixing
this is just a matter of doing s/MAX_PATH/MAXPGPATH/ in dirmod.c.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Adding facility for injection points (or probe points?) for more advanced tests
Next
From: Dean Rasheed
Date:
Subject: Re: MERGE ... RETURNING