| 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 00:57:04 |
| Message-ID: | 20140111005704.GD15692@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 9, 2014 at 01:03:08PM -0500, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > I was referring to the analyze-in-stages logic, which is not specific
> > to 8.4. I don't see a reason not to put that into vacuumdb.
>
> Right, that's Peter's core proposal, which I agreed with. The issue
> was what to do with some other steps that pg_upgrade sometimes sticks
> into the analyze_new_cluster.sh script.
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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2014-01-11 01:02:35 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |
| Previous Message | Jim Nasby | 2014-01-11 00:51:41 | Re: Standalone synchronous master |