Re: pg_upgrade output directory - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_upgrade output directory
Date
Msg-id 201006120358.o5C3wbN11933@momjian.us
Whole thread Raw
In response to pg_upgrade output directory  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pg_upgrade output directory
List 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@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + None of us is going to be here forever. +


pgsql-hackers by date:

Previous
From: Rafael Martinez
Date:
Subject: 9.0beta2 - server crash when using HS + SR
Next
From: Peter Eisentraut
Date:
Subject: Re: PG 9.1 tentative timeline