Re: pg_dump -Ft failed on Windows XP - Mailing list pgsql-hackers

From Zeugswetter Andreas DCP SD
Subject Re: pg_dump -Ft failed on Windows XP
Date
Msg-id E1539E0ED7043848906A8FF995BDA579F318AB@m0143.s-mxs.net
Whole thread Raw
In response to pg_dump -Ft failed on Windows XP  (Yoshiyuki Asaba <y-asaba@sraoss.co.jp>)
Responses Re: pg_dump -Ft failed on Windows XP
List pgsql-hackers
> >> Apparently it won't work at all if TMP isn't set?
>
> > I'm not *too* concerned about that, since TMP is normally set by the
OS
> > itself. There's one set in the "system environment" (to
c:\windows\temp
> > or whatrever) and then it's overridden by one set by the OS when it
> > loads a user profile.
>
> OK, then maybe not having it would be equivalent to /tmp-not-writable
> on Unix, ie, admin error.
>
> > Also to the point, what would you fall back to?
>
> Current directory maybe?

It tries \ (tested on Win 2000), if the dir argument is NULL and TMP is
not set.
But TMP is usually set.

Attached is a working version not yet adapted to port/.
- memoryleak fixed
- use _tmpname and _fdopen not the compatibility tmpname and fdopen
(imho only cosmetic)
- EACCES fixed (Win2000 needs _S_IREAD | _S_IWRITE or fails with EACCES,
even as Admin)
- I suggest adding a prefix pg_temp_ (for leftover temp files after
crash,
    the name I get is then usually pg_temp_2)

Andreas

Attachment

pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: Google SoC--Idea Request
Next
From: "Gevik Babakhani"
Date:
Subject: TODO item question [pg_hba.conf]