| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, Anssi Kääriäinen <anssi(dot)kaariainen(at)thl(dot)fi>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER EXTENSION UPGRADE, v3 |
| Date: | 2011-02-03 18:10:12 |
| Message-ID: | E105791A-0950-4AAC-9A05-FCDE1F8CE814@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 3, 2011, at 10:07 AM, Tom Lane wrote:
> Well, pg_upgrade is designed to work within a major-version series, eg
> you could do a 9.1-to-9.1 upgrade if you needed to install a newer
> version of an extension. Admittedly, this is swinging a rather larger
> hammer than "apply an upgrade script" would entail.
Dude. That's a frigging piledriver!
> But I'm still not
> convinced that we need to expend a great deal of work on making that
> process a tad more efficient.
Agreed. I would handle simple extension upgrades not with pg_upgrade, but the same way I do now. Think about how one currently jumps from PostGIS 1.4 to 1.5.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-02-03 18:17:08 | Re: [HACKERS] Slow count(*) again... |
| Previous Message | Tom Lane | 2011-02-03 18:07:31 | Re: ALTER EXTENSION UPGRADE, v3 |