| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Alexandra Wang <alexandra(dot)wang(dot)oss(at)gmail(dot)com>, Chris Travers <chris(dot)travers(at)stormatics(dot)tech>, Farooq Rashed <farooq(dot)rashed(at)desc(dot)gov(dot)ae>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_rewind fails on Windows where tablespaces are used |
| Date: | 2025-01-08 14:45:19 |
| Message-ID: | 039f5e85-6059-4c94-bf0b-20c38b9e24e3@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2024-11-27 We 7:52 AM, Andrew Dunstan wrote:
>
> 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.
>
>
>
Those patches didn't actually include any tests. I guess the best test
would be to create a chain of several junction points and then run
initdb on the leaf of the chain?
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2025-01-08 20:52:29 | Re: BUG #18765: Inconsistent behaviour and errors with LIKE |
| Previous Message | Thomas Munro | 2025-01-08 03:48:03 | Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows |