| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Is this a bug? |
| Date: | 2018-02-14 12:35:00 |
| Message-ID: | 20180214.213500.533982224455602757.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2018-02-14 14:16:42 | Re: Is this a bug? |
| Previous Message | Amit Kapila | 2018-02-14 12:14:56 | Re: [HACKERS] Restrict concurrent update/delete with UPDATE of partition key |