X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 12CD611F6D5A for ; Thu, 20 Apr 2006 14:55:40 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.375 X-Spam-Level: X-Spam-Status: No, score=-2.375 required=5 tests=[AWL=0.226, BAYES_00=-2.599, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id FeOhlnNQUNJZ for ; Thu, 20 Apr 2006 14:55:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 6792811F66F1 for ; Thu, 20 Apr 2006 14:55:22 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k3KHtMu3026305; Thu, 20 Apr 2006 13:55:22 -0400 (EDT) To: "Magnus Hagander" cc: "Peter Eisentraut" , pgsql-hackers@postgresql.org, "Yoshiyuki Asaba" Subject: Re: pg_dump -Ft failed on Windows XP In-reply-to: <6BCB9D8A16AC4241919521715F4D8BCEA0F91E@algol.sollentuna.se> References: <6BCB9D8A16AC4241919521715F4D8BCEA0F91E@algol.sollentuna.se> Comments: In-reply-to "Magnus Hagander" message dated "Thu, 20 Apr 2006 19:35:34 +0200" Date: Thu, 20 Apr 2006 13:55:21 -0400 Message-ID: <26304.1145555721@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200604/742 X-Sequence-Number: 82465 "Magnus Hagander" writes: >> 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? Actually, the thing that struck me about the man page was that first it said current dir was a fallback, and then it said it wasn't. Is this just typical Microsoft brain damage, or is there a reason to avoid using current dir for this? regards, tom lane