From: zz_11@mail.bg
To: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: very slow postgresql startup
Date: Mon, 23 May 2016 09:49:09 -0000
Message-ID: <297fe58606ee5f5fbbc80aa082e0d154.mailbg@mail.bg> (raw)
In-Reply-To: <CABUevEyvq=3HnDrbRAA-FOAGZ7eJSF=9kak3Cbm97EHOWe=Deg@mail.gmail.com>
References: <CABUevEyvq=3HnDrbRAA-FOAGZ7eJSF=9kak3Cbm97EHOWe=Deg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Hi,
Thank you.
Any idea how to view the progress?
Regards,
Ivan.
----- Цитат от Magnus Hagander (magnus@hagander.net), на
23.05.2016 в 11:28 -----
On May 23, 2016 10:35, wrote:
>
> Hi,
>
>
> After stopping my pg server with pg_ctl -m immediate stop options it
take hours to startup.
>
> With vmstat I find hi pcu and io useages.
>
> Any idea about this problem? I think it can be pg_xlog files.
>
> How can I debug or trace this problem?
>
> pg version is 9.4.5 running on centos 6.
This is not uncommon when you shutdown with immediate. It's the main reason
you should normally use fast and not immediate.
And yes, it's likely the replay of xlog. Hours is a very long time though,
but with very high checkpoint timeout that's certainly possible.
/Magnus
Links:
------
[1] mailto:zz_11@mail.bg
-------------------------------------
ПП: Видя ли специалните предложения на СуперХостинг.БГ? Ако имаш идеи за сайт, това е правилното място!
http://www.superhosting.bg/promo/spring?utm_source=MailBG&utm_medium=footer&utm_content=v2&a...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: zz_11@mail.bg, magnus@hagander.net
Subject: Re: very slow postgresql startup
In-Reply-To: <297fe58606ee5f5fbbc80aa082e0d154.mailbg@mail.bg>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox