| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Murthy Nunna <mnunna(at)fnal(dot)gov>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_upgrade 10.2 |
| Date: | 2018-06-12 21:13:27 |
| Message-ID: | 5f0d7335-e681-56bb-7d14-cf97fccb1bcf@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general pgsql-performance |
On 06/12/2018 01:58 PM, Murthy Nunna wrote:
> Thanks Adrian.
> I removed "-k" flag. But still got same error.
>
> There seems to be a postmaster servicing the old cluster.
> Please shutdown that postmaster and try again.
> Failure, exiting
>
Well according to the code in pg_upgrade.c that message should not be
reached when the check option is specified:
if (!user_opts.check)
pg_fatal("There seems to be a postmaster servicing the old
cluster.\n"
"Please shutdown that postmaster and try again.\n");
else
*live_check = true;
Can we see the actual command you ran?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Murthy Nunna | 2018-06-12 21:18:07 | RE: pg_upgrade 10.2 |
| Previous Message | Murthy Nunna | 2018-06-12 20:58:25 | RE: pg_upgrade 10.2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Murthy Nunna | 2018-06-12 21:18:07 | RE: pg_upgrade 10.2 |
| Previous Message | Alexander Shutyaev | 2018-06-12 21:11:08 | Re: pg_upgrade and wraparound |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Murthy Nunna | 2018-06-12 21:18:07 | RE: pg_upgrade 10.2 |
| Previous Message | Murthy Nunna | 2018-06-12 20:58:25 | RE: pg_upgrade 10.2 |