| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Extensions versus pg_upgrade |
| Date: | 2011-02-08 18:26:45 |
| Message-ID: | B778EB02-757F-421E-86D8-36974DD132BC@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 8, 2011, at 10:24 AM, Tom Lane wrote:
>> Ah, right, of course. I don't suppose CREATE OR REPLACE would work, either, in some cases at least?
>
> But figuring out just what commands to issue is pretty nearly AI-complete.
> The whole point of ALTER EXTENSION UPGRADE is to have a human do that
> and then give you a script to run.
Damn. Okay, was just trying to think outside the box a bit here.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-02-08 18:30:55 | pgsql: Basic Recovery Control functions for use in Hot Standby. Pause, |
| Previous Message | Tom Lane | 2011-02-08 18:24:28 | Re: Extensions versus pg_upgrade |