From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(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 13:44:08 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCEA352D4@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > 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.
Well, you're never gonig to convince MS of that :-)
And either way, the runtime we're usnig now isn't especially current
(MSVC6), so even in the unlikely event that they did fix it, it wouldn't
help us. So we'll definitly need to fix it ourselves. Did the code I
sent the last time look reasonable?
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-20 14:00:48 | Re: pg_dump -Ft failed on Windows XP |
Previous Message | Robert Treat | 2006-04-20 12:55:13 | Re: please change url for czech postgresql site |