Re: Postgresql 9.3 not coming up after restart in centos

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: "balajishanmugam(at)live(dot)in" <balajishanmugam(at)live(dot)in>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgresql 9.3 not coming up after restart in centos
Date: 2016-01-06 19:52:43
Message-ID: CAOR=d=0MsHrGf+HygLAz8NZudNYCieJA9mXj4GP0X9MSJ8WvNw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jan 6, 2016 at 12:36 PM, balajishanmugam(at)live(dot)in
<balajishanmugam(at)live(dot)in> wrote:
> By application I mean centOS.
>
> We are starting and stopping Postgres using systemd service. We have a
> service file called postgresql9.3.service which is used to start or stop
> Postgres.
>
> Excerpts of postgresql9.3.service
>
> ExecStartPre=/usr/pgsql-9.3/bin/postgresql93-check-db-dir ${PGDATA}
> ExecStart=/usr/pgsql-9.3/bin/pg_ctl start -D ${PGDATA} -s -w -t 300
> ExecStop=/usr/pgsql-9.3/bin/pg_ctl stop -D ${PGDATA} -s -m fast
> ExecReload=/usr/pgsql-9.3/bin/pg_ctl reload -D ${PGDATA} -s
>
>

So how are you restarting centos? Orderly shutdown, pulling the power plugs etc?

I'm wondering if you've got untrustworthy data storage underneath it
(i.e. storage that lies about fsync) and maybe centos or the method of
shutdown isn't allowing the drives to flush the data that they've
already said they flushed but actually haven't.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2016-01-06 20:31:11 Re: BUG #13847: WARNING: skipping "pg_toast_" --- cannot vacuum indexes, views, or special system tables VACUUM
Previous Message balajishanmugam@live.in 2016-01-06 19:36:08 Re: Postgresql 9.3 not coming up after restart in centos