| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | robertmhaas(at)gmail(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Is this a bug? |
| Date: | 2018-02-14 22:26:44 |
| Message-ID: | 20180215.072644.827386827016019315.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> "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.
I didn't know that recovery conflict could happen even with buffer
pin. I should have examined the source code first. Sorry for noise.
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 | Pierre Ducroquet | 2018-02-14 22:32:17 | Re: JIT compiling with LLVM v10.1 |
| Previous Message | Tom Lane | 2018-02-14 21:49:13 | Re: tapeblocks is uninitialized in logtape.c |