Re: Making pgxs builds work with a relocated installation - Mailing list pgsql-hackers

From Dave Page
Subject Re: Making pgxs builds work with a relocated installation
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC2EEB@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Making pgxs builds work with a relocated installation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

> -----Original Message-----
> From: Magnus Hagander [mailto:mha@sollentuna.net]
> Sent: 27 September 2005 09:19
> To: Dave Page; Tom Lane; Peter Eisentraut
> Cc: pgsql-hackers@postgresql.org
> Subject: RE: [HACKERS] Making pgxs builds work with a
> relocated installation
>
> > If it's disabled, then they aren't going to be able to use
> > short names anyway, therefore we can't do much about it. If
> > you see what I mean!
>
> Well, are we sure thare are no other ways? Either some funky
> quoting or
> backslash-escaping spaces or something like that?

Tried quoting and '\ '. Neither work.

> > If GetShortPathName() just returns what was passed to it in
> > such cases, then at least we won't be any worse off than we are now.
>
> Right. That'll have to be checked though, the API docs don't seem to
> talk about that. Could be it gives you NULL or something
> equally evil..

Well, knowing you you have a VM setup in this way so testing should be
easy enough :-p

/D


pgsql-hackers by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: Making pgxs builds work with a relocated installation
Next
From: Andrey Repko
Date:
Subject: Strange, very strange