Re: pg_rewind fails on Windows where tablespaces are used

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>

To: Thomas Munro <thomas.munro@gmail.com>, Michael Paquier <michael@paquier.xyz>

Cc: Alexandra Wang <alexandra.wang.oss@gmail.com>, Chris Travers <chris.travers@stormatics.tech>, Farooq Rashed <farooq.rashed@desc.gov.ae>, pgsql-bugs@lists.postgresql.org

Date: 2024-11-27T12:52:16Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix readlink() for non-PostgreSQL junction points on Windows.
- 2c4a532c96a9 13.19 landed
- f4fd5325cc87 14.16 landed
- 9b136b0f2e53 15.11 landed
Fix stat() for recursive junction points on Windows.
- fbf8efbda88c 13.19 landed
- 9f1c67488e59 14.16 landed
- e708f31881fd 15.11 landed
Fix pg_rewind with in-place tablespaces when source is remote
- bf227926d22b 17.0 cited
Make unlink() work for junction points on Windows.
- f357233c9db8 16.0 cited
Use in-place tablespaces in regression test.
- d6d317dbf615 15.0 cited

On 2024-11-26 Tu 8:58 PM, Thomas Munro wrote:
> It might be worth checking if 4517358e and f71007fb should be
> back-patched too.  There was a brief discussion[1], but no one with
> Windows-testing capabilities was around and it didn't seem too
> serious, and then there was the whole re-wrap and it seemed best to
> keep out of the way of that.  But now that the coast is clear...
>
> [1] https://www.postgresql.org/message-id/CAD5tBcKnE3C1hycBYZYtYpNssQR_e%2Bu2%3DCmDhGRFvDMEg3onRg%40mail.gmail.com



Yes, it's on my TODO list. Have been waiting for a) the releases to 
settle down b) getting availability of Windows resources again and c) 
being back at my home location. All three are now met, so will work on it.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com