| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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:21:18 |
| Message-ID: | 20140111012118.GE15692@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 10, 2014 at 08:15:53PM -0500, Tom Lane wrote:
> 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.
If it is one command, why use a script? Just give them the command.
> 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?
Uh, I didn't think enough people scripted pg_upgrade to be worth it.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2014-01-11 01:21:44 | Re: Standalone synchronous master |
| Previous Message | Tom Lane | 2014-01-11 01:15:53 | Re: integrate pg_upgrade analyze_new_cluster.sh into vacuumdb |