From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade output directory |
Date: | 2010-06-12 03:58:37 |
Message-ID: | 201006120358.o5C3wbN11933@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
> Why does pg_upgrade create its output directory in the user's home
> directory (or TMP on Windows)? I should have thought that the current
> working directory would be a more suitable choice. At the very least
> there should be an option for where to create it. Also, this location
> doesn't seem to be referred to at all in the docs.
Yeah, it is odd. I did it that way because the output files need to
exist after the utility is run, and I worried that putting them in the
current directory might cause them to be accidentally deleted or
overlooked.
However, I might have been too conservative. How do tools that generate
multiple output files usually handle this situation? Do they output in
to a subdirectory in $HOME, or in a subdirectory of the current
directory, or just create multiple files without a subdirectory?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2010-06-12 05:45:12 | Re: PG 9.1 tentative timeline |
Previous Message | Rafael Martinez | 2010-06-12 01:29:04 | 9.0beta2 - server crash when using HS + SR |