Re: Using pg_upgrade on log-shipping standby servers

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Using pg_upgrade on log-shipping standby servers
Date: 2012-07-23 20:11:27
Message-ID: 1343074287.3602.1.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On mån, 2012-07-23 at 10:08 -0400, Robert Haas wrote:
> Relying on the number of hard links seems very fragile. For example,
> it'll break if you are using copy mode. And it won't work on Windows,
> either.

pg_upgrade could remember the list of files that the user would need to
copy to the remote server (i.e., the list of files pg_upgrade itself
copied or linked) and write that to a file.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2012-07-23 21:27:12 Re: [patch] libpq one-row-at-a-time API
Previous Message Noah Misch 2012-07-23 19:10:36 Re: 9.2 release schedule