| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "Leonardo M(dot) Ramé" <l(dot)rame(at)griensu(dot)com>, Claudio Biasatti <c(dot)biasatti(at)griensu(dot)com>, PostgreSql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Error while upgrading from 8.4 to 9.3 |
| Date: | 2014-05-30 12:00:44 |
| Message-ID: | 20140530120044.GA5601@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, May 28, 2014 at 11:28:47PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > On Wed, May 28, 2014 at 04:56:53PM -0700, Adrian Klaver wrote:
> >> So for my edification, does that mean -O ' -c
> >> config_file=/etc/postgresql/9.3/main/postgresql.conf' could cause a
> >> problem or that starting Postgres outside pg_upgrade could cause a
> >> problem, or both.
>
> > Starting Postgres outside pg_upgrade would _certainly_ cause a problem.
>
> It appeared to me that it was failing safely, ie, once somebody had
> started a conflicting postmaster, pg_upgrade's attempt to start one
> failed without damage.
Yes, it was. The thing we can't block is an administrator starting the
old or new postmaster while pg_upgrade isn't using it, then shutting it
down before pg_upgrade needs it --- seems unlikely though.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martín Marqués | 2014-05-30 12:43:53 | Re: Data Checksum feature and streaming replication |
| Previous Message | snowsnake | 2014-05-30 08:59:46 | database system was interrupted sometimes untill we restart it can be used |