From: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
---|---|
To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
Cc: | "List, Postgres" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: hot_standby_feedback |
Date: | 2013-09-16 08:24:44 |
Message-ID: | CADmi=6N-YcPmeoK=4n-idp9AqLn_siVjPKMVJv_t8PBddiffjA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Aug 29, 2013 at 2:44 PM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
> I have a question about hot_standby_feedback parameter. In my
> understanding, if this parameter is on, a long running transaction on
> standby will not be canceled even if the transaction conflicts.
> As you can see vacuum on the primary removes all the rows in t1. I
> thought vacuum will not make the page entriely empty because
> of the effect of hot_standby_feedback.
>
> After while, on standby:
> test=# select * from t1;
> FATAL: terminating connection due to conflict with recovery
> DETAIL: User was holding a relation lock for too long.
> HINT: In a moment you should be able to reconnect to the database and repeat your command.
>
> Again, this is not what I expected. Am I missing something?
I also expected this behavior, and suffer similar problems with
PostgreSQL 9.1. I reported this as BUG #7546 with a test case and
raised it a few times on the mailing lists, but am no closer to a
solution.
From | Date | Subject | |
---|---|---|---|
Next Message | Ladislav Lenart | 2013-09-16 09:58:53 | [PG9.1] CTE usage |
Previous Message | Albe Laurenz | 2013-09-16 07:32:40 | Re: Rename extension? |