| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is this a bug? |
| Date: | 2018-02-14 14:18:20 |
| Message-ID: | CA+TgmoYcaxG+Sn3rD=dn+x9Q6S5_Vn5qsSP3o-x8QUOgmXRVNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 14, 2018 at 7:35 AM, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> 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.
Sounds normal to me. Maybe the message could use some work, but this
is how hot standby works: if max_standby_archive_delay or
max_standby_streaming_delay expires, whatever is blocking recovery
gets blasted out of the way.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-02-14 14:27:04 | Kerberos test suite |
| Previous Message | Sergei Kornilov | 2018-02-14 14:16:42 | Re: Is this a bug? |