Re: gcc 4.6 and hot standby
От | Alex Hunsaker |
---|---|
Тема | Re: gcc 4.6 and hot standby |
Дата | |
Msg-id | BANLkTik55wN_urFw=RU9EbQU1-ZApxGD3Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: gcc 4.6 and hot standby (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: gcc 4.6 and hot standby
Re: gcc 4.6 and hot standby |
Список | pgsql-hackers |
On Wed, Jun 8, 2011 at 12:49, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Alex Hunsaker <badalex@gmail.com> writes: >> So I've been delaying moving some production boxes over to 9.0.4 from >> 2011-06-08 11:41:03 MDT [6078]: [1-1] user= FATAL: terminating >> walreceiver process due to administrator command >> [ repeats... ] > >> I suppose the next step is to narrow it down to a specific flag -O2 >> uses... But I thought I would post here first-- maybe someone else has >> hit this? Or maybe someone has a bright idea on how to narrow this >> down? > > Maybe using a "prerelease" gcc version isn't such a hot idea for > production. It's very, very, very difficult to see how the behavior you > describe isn't a compiler bug. Yeah :-). However ill note it looks like its the default compiler for fedora 15, ubuntu natty and debian sid. > It might be useful to strace the postmaster and walreceiver processes > just to see if any signal is actually being sent or received. Will do.
В списке pgsql-hackers по дате отправления: