Re: BUG #14588: Postgres process blocked on semop

From: Neo Liu <diabloneo(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14588: Postgres process blocked on semop
Date: 2017-03-12 06:21:31
Message-ID: CAF_Sdb9A-1qEeH82-nd-e4Jx9YYHR1zswfSAnx=0FqTpa6vD6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Content of my pg_hba.conf

local all all peer
host all all 0.0.0.0/0 md5
host replication demon_replicator 0.0.0.0/0 md5

diabloneo

On Sun, Mar 12, 2017 at 12:53 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> diabloneo(at)gmail(dot)com writes:
> > During the daytime, there are about 300 postgres processes running, work
> as
> > expected. On 00:00 each day, there will be about 200 more postgresql
> > processes created, now totally about 500. And from that time, thoese
> working
> > processes are all blocked on semop function. I check this using pstack
> > command, and also check the output of ipcs -s [-i]. After this has
> happened,
> > all new connection will stay in state authentication.
>
> And your authentication setup is ...?
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-03-12 16:30:44 Re: BUG #14588: Postgres process blocked on semop
Previous Message Tom Lane 2017-03-12 04:53:10 Re: BUG #14588: Postgres process blocked on semop