| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nagy László Zsolt <gandalf(at)shopzeus(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Could not shut down DB |
| Date: | 2016-05-30 16:43:11 |
| Message-ID: | 12880.1464626591@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
=?UTF-8?Q?Nagy_L=c3=a1szl=c3=b3_Zsolt?= <gandalf(at)shopzeus(dot)com> writes:
> I could stop it with:
> pg_ctl stop -i i
> but before that:
> May 30 07:21:00 appserver postgres[65202]: [5-1] FATAL: the database
> system is shutting down
> May 30 07:21:00 appserver postgres[65203]: [5-1] FATAL: the database
> system is shutting down
> May 30 07:21:00 appserver postgres[65206]: [5-1] FATAL: the database
> system is shutting down
> It happened in the weekend, and the server log does not contain anything
> except these "FATAL: shutting down" messages, so I'm not able to tell
> when is started. Any idea what could possible cause this error?
Well, the default-until-recently "smart" shutdown mode would wait for
all existing sessions to finish, while not letting any new ones in.
That sure looks like what you have here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael JOIGNY | 2016-05-31 14:39:35 | could not read block 0 in file "base/mydb/myfile": read only 0 of 8192 bytes |
| Previous Message | Alex Ignatov | 2016-05-30 16:29:15 | Re: very slow postgresql startup |