Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b4mVx-0003sz-3q for pgsql-admin@arkaria.postgresql.org; Mon, 23 May 2016 09:51:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b4mVv-0002ks-Ka for pgsql-admin@arkaria.postgresql.org; Mon, 23 May 2016 09:51:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b4mUD-0000mP-5c for pgsql-admin@postgresql.org; Mon, 23 May 2016 09:49:21 +0000 Received: from mx3.mail.bg ([193.201.172.119]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b4mU3-0007tC-Cr for pgsql-admin@postgresql.org; Mon, 23 May 2016 09:49:20 +0000 Received: from mail.bg (unknown [10.0.0.31]) by mx3.mail.bg (Postfix) with ESMTPA id 46B10202A7E7; Mon, 23 May 2016 12:49:09 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1463996949; bh=T4ldU+I8vB5689fLtOM//7EFG3aZtkY8tfobSimetvY=; h=Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc: MIME-Version:Content-Type; b=p+vENXMKSXcbFbOmgsTh60dr4R/rRUYoVnVBDnxw8sHa7112LfGUGa2QngHoysj1i VgbpxFpRi5h8FD/OSH72a6AOzG0f/0ax41ykFjHO3O7SsZyMKiPfkv4m/yZX0XOMcl zTQYZp6DKTYfQqhTiD2mTrgSqvyizbJoMsk/QXWg= Message-ID: <297fe58606ee5f5fbbc80aa082e0d154.mailbg@mail.bg> In-Reply-To: References: Date: Mon, 23 May 2016 09:49:09 -0000 Subject: Re: very slow postgresql startup From: zz_11@mail.bg To: Magnus Hagander Cc: pgsql-admin User-Agent: Mail.BG Webmail MIME-Version: 1.0 Content-Type: multipart/alternative;boundary="----=_20160523094908_93785" X-Priority: 3 (Normal) Importance: Normal X-Composed: 2016-05-23T09:49:08+00:00 X-Originating-IP: [94.156.95.6] X-Checking: 2016-05-23T09:49:08+00:00 X-Checked: 2016-05-23T09:49:09+00:00 X-Pg-Spam-Score: -3.9 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org ------=_20160523094908_93785 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable =0A=0A=0AHi,=0A=0A=0AThank you.=0A=0A=0AAny idea how to view the progress?= =0A=0A=0ARegards,=0A=0A=0AIvan.=0A=0A=0A----- =D0=A6=D0=B8=D1=82=D0=B0= =D1=82 =D0=BE=D1=82 Magnus Hagander (magnus@hagander.net), =D0=BD=D0=B0=0A2= 3.05.2016 =D0=B2 11:28 ----- =0A=0A=0A On May 23, 2016 10:35, wrote:=0A >= =0A > Hi,=0A >=0A >=0A > After stopping my pg server with pg_ctl -m immedia= te stop options it=0Atake hours to startup.=0A >=0A > With vmstat I find hi= pcu and io useages.=0A >=0A > Any idea about this problem? I think it can = be pg_xlog files.=0A >=0A > How can I debug or trace this problem?=0A >=0A = > pg version is 9.4.5 running on centos 6.=0A=0A=0AThis is not uncommon whe= n you shutdown with immediate. It's the main reason=0Ayou should normally u= se fast and not immediate. =0A=0A=0AAnd yes, it's likely the replay of xlo= g. Hours is a very long time though,=0Abut with very high checkpoint timeou= t that's certainly possible. =0A=0A=0A/Magnus=0A=0A=0A=0A=0ALinks:=0A-----= -=0A[1] mailto:zz_11@mail.bg=0A=0A=0A-------------------------------------= =0A=0A=D0=9F=D0=9F: =D0=92=D0=B8=D0=B4=D1=8F =D0=BB=D0=B8 =D1=81=D0=BF= =D0=B5=D1=86=D0=B8=D0=B0=D0=BB=D0=BD=D0=B8=D1=82=D0=B5 =D0=BF=D1=80=D0= =B5=D0=B4=D0=BB=D0=BE=D0=B6=D0=B5=D0=BD=D0=B8=D1=8F =D0=BD=D0=B0 =D0=A1= =D1=83=D0=BF=D0=B5=D1=80=D0=A5=D0=BE=D1=81=D1=82=D0=B8=D0=BD=D0=B3.=D0= =91=D0=93? =D0=90=D0=BA=D0=BE =D0=B8=D0=BC=D0=B0=D1=88 =D0=B8=D0=B4=D0= =B5=D0=B8 =D0=B7=D0=B0 =D1=81=D0=B0=D0=B9=D1=82, =D1=82=D0=BE=D0=B2=D0= =B0 =D0=B5 =D0=BF=D1=80=D0=B0=D0=B2=D0=B8=D0=BB=D0=BD=D0=BE=D1=82=D0=BE = =D0=BC=D1=8F=D1=81=D1=82=D0=BE!=0A http://www.superhosting.bg/promo/spring?= utm_source=3DMailBG&utm_medium=3Dfooter&utm_content=3Dv2&utm_campaign=3DSpr= ing2016 ------=_20160523094908_93785 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Hi,

Thank you.


<= p valid=3D"true" style=3D"line-height: 16px; font-size: 13px; font-family: = Tahoma, sans-serif; margin: 16px 0px;">Any idea how to view the progress?


Regards,

Ivan.<= /p>

=0A

----- =D0=A6=D0=B8=D1=82=D0=B0=D1=82 =D0=BE=D1=82 Magnus Hagan= der (magnus@hagander.net), =D0=BD=D0=B0 23.05.2016 =D0=B2 11:28 -----

=0A
=0A


=0AOn May = 23, 2016 10:35, <zz_11@mail.bg> = wrote:
=0A>
=0A> Hi,
=0A>
=0A>
=0A> After sto= pping my pg server with pg_ctl -m immediate stop options it take hours= to startup.
=0A>
=0A> With vmstat I find hi pcu and io useages= .
=0A>
=0A> Any idea about this problem? I think it can be pg_x= log files.
=0A>
=0A> How can I debug or trace this problem?
= =0A>
=0A> pg version is 9.4.5 running on centos 6.

=0A

This is not uncommon when you shutdown with immediate. It's the m= ain reason you should normally use fast and not immediate.

=0A

And yes, it's likely the replay of xlog. Hours is a very long time th= ough, but with very high checkpoint timeout that's certainly possible.

= =0A

/Magnus
=0A

=0A
=0A

=0A

---= ----------------------------------
=0A=D0=9F=D0=9F: =D0=92=D0=B8=D0=B4=D1=8F =D0= =BB=D0=B8 =D1=81=D0=BF=D0=B5=D1=86=D0=B8=D0=B0=D0=BB=D0=BD=D0=B8=D1=82= =D0=B5 =D0=BF=D1=80=D0=B5=D0=B4=D0=BB=D0=BE=D0=B6=D0=B5=D0=BD=D0=B8=D1= =8F =D0=BD=D0=B0 =D0=A1=D1=83=D0=BF=D0=B5=D1=80=D0=A5=D0=BE=D1=81=D1=82= =D0=B8=D0=BD=D0=B3.=D0=91=D0=93? =D0=90=D0=BA=D0=BE =D0=B8=D0=BC=D0=B0= =D1=88 =D0=B8=D0=B4=D0=B5=D0=B8 =D0=B7=D0=B0 =D1=81=D0=B0=D0=B9=D1=82, = =D1=82=D0=BE=D0=B2=D0=B0 =D0=B5 =D0=BF=D1=80=D0=B0=D0=B2=D0=B8=D0=BB=D0= =BD=D0=BE=D1=82=D0=BE =D0=BC=D1=8F=D1=81=D1=82=D0=BE!
=0A ------=_20160523094908_93785--