| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Is this a bug? |
| Date: | 2018-02-14 16:54:19 |
| Message-ID: | 20180214165419.jnlbjpcipa6dld4p@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-02-14 21:35:00 +0900, Tatsuo Ishii wrote:
> Today one of Pgpool-II users reported an interesting fatal error
> message from PostgreSQL:
>
> FATAL: terminating connection due to conflict with recovery
> DETAIL: User was holding shared buffer pin for too long.
> HINT: In a moment you should be able to reconnect to the database and repeat your command.
>
> "User was holding shared buffer pin for too long" sounds unusual to
> me. Is this a bug? PostgreSQL version is 10.1 according to the user.
Sorry to be the grumpy guy: This isn't the -general list. Nor -bugs. And
a quick search for it in the source code and/or search engines will show
some hits as well.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2018-02-14 17:06:45 | Re: tapeblocks is uninitialized in logtape.c |
| Previous Message | Tom Lane | 2018-02-14 16:51:54 | Re: master plpython check fails on Solaris 10 |