From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, "Yoshiyuki Asaba" <y-asaba(at)sraoss(dot)co(dot)jp> |
Subject: | Re: pg_dump -Ft failed on Windows XP |
Date: | 2006-04-20 11:53:30 |
Message-ID: | 200604201353.31774.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Am Donnerstag, 20. April 2006 13:21 schrieb Magnus Hagander:
> It's not buggy. It's well documented behaviour,and per my linux manpage
> for the file it's also OK per spec:
>
> The standard does not specify the directory that tmpfile()
> will use. Glibc will try the path prefix P_tmpdir defined
> in <stdio.h>, and if that fails the directory /tmp.
The spec says
The tmpfile() function shall create a temporary file and open a
corresponding stream. The file shall be automatically deleted when all
references to the file are closed. The file is opened as in fopen() for
update (w+).
If the implementation is such that it tries to create the file in a directory
that the user does not have write permission to, it's a bug.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2006-04-20 12:51:25 | Re: Google SoC--Idea Request |
Previous Message | Magnus Hagander | 2006-04-20 11:21:13 | Re: pg_dump -Ft failed on Windows XP |