Re: pg_upgrade del/rmdir path fix - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pg_upgrade del/rmdir path fix
Date
Msg-id 50450FB4.9000305@dunslane.net
Whole thread Raw
In response to Re: pg_upgrade del/rmdir path fix  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_upgrade del/rmdir path fix  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 09/03/2012 03:22 PM, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> This time with a patch.
> Nitpicky gripe: "fix_path" is a mighty generic name.  How about
> "fix_path_for_windows" or something like that?  I don't think I'd
> mark it inline, either.
>
> More generally, the behavior of combining two (maybe) filename segments
> seems overcomplicated and unnecessary.  Why not just have it take *one*
> argument and back-slashify that, without the concatenation behavior?
> Then you'd have two calls instead of one at some of the call sites,
> but that doesn't seem like much of a loss.  The malloc'd strings are
> getting leaked anyway.  The function itself would reduce to pg_strdup
> and a backslashification loop.  Also, you could turn it into a complete
> no-op (not even pg_strdup) on non-Windows.
>
>


OK, revised patch attached.

cheers

andrew

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Multiple setup steps for isolation tests
Next
From: Tom Lane
Date:
Subject: Re: Proof of concept: standalone backend with full FE/BE protocol