Re: integrate pg_upgrade analyze_new_cluster.sh into vacuumdb

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: integrate pg_upgrade analyze_new_cluster.sh into vacuumdb
Date: 2014-01-11 01:15:53
Message-ID: 20706.1389402953@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I assume pg_upgrade would just tell the user what vacuumdb command to
> run, rather than create a script to call it. If they have to run two
> commands, we will output the two commands.

Why would we change the operational procedure of "run this script
after pg_upgrade"? It just complicates life for users.

Bear in mind also that some may have scripted the call of the script
already, so you'd be breaking their scripts; to achieve what?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2014-01-11 01:21:18 Re: integrate pg_upgrade analyze_new_cluster.sh into vacuumdb
Previous Message Adrian Klaver 2014-01-11 01:06:58 Re: Standalone synchronous master