Re: pg_upgrade output directory

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade output directory
Date: 2010-06-12 10:57:38
Message-ID: AANLkTiniY3i1Iwl1f2a3syOmUL0-AvE521-bbs06l6BR@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 12, 2010 at 4:58 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> 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?

Generally they put them in the current directory without
subdirectories but take a parameter to specify a directory to use.
That parameter could be mandatory though if you're afraid the current
directory isn't a suitable place.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian Pflug 2010-06-12 11:50:08 Re: Proposal for 9.1: WAL streaming from WAL buffers
Previous Message Peter Eisentraut 2010-06-12 08:04:11 Re: hstore ==> and deprecate =>