| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Sam Saffron <sam(dot)saffron(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Failure upgrading PG 9.2 to 9.3 |
| Date: | 2014-03-26 00:20:06 |
| Message-ID: | 53321D36.3030900@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 03/25/2014 05:14 PM, Sam Saffron wrote:
> 9.2 is the problem instance, 9.3 is clean, I am able to do many
> upgrades without issues with the same script (which spawns a clean 9.3
> instance and then pg_upgrades to it.)
Alright that makes sense, though I am still unclear about the below from
your original post:
Selecting previously unselected package postgresql-9.2.
Unpacking postgresql-9.2 (from
.../postgresql-9.2_9.2.8-1.pgdg12.4+1_amd64.deb) ...
Processing triggers for postgresql-common ...
Setting up postgresql-client-9.2 (9.2.8-1.pgdg12.4+1) ...
Setting up postgresql-9.2 (9.2.8-1.pgdg12.4+1) ...
If the 9.2 instance was already there, why was 9.2 being installed? Is
it possible that it was installed over a running version?
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2014-03-26 01:33:03 | Re: Trimming transaction logs after extended WAL archive failures |
| Previous Message | Sam Saffron | 2014-03-26 00:14:51 | Re: Failure upgrading PG 9.2 to 9.3 |