From: | Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)com> |
---|---|
To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Get hot_standby_feedback messages |
Date: | 2022-07-27 05:13:56 |
Message-ID: | CAFpL5VwJuUxtnf9_kHcLt=pGTUL5sB0r62M2DihajcNO5ti_oA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
We are unable to determine the transaction for xmin that is holding back
the slots.
--- I am not sure if this is a bug, but Is there any way we can find this
data and debug more?
Thanks,
Nikhil
On Sat, Jul 23, 2022 at 11:43 AM Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)com>
wrote:
> Hi,
>
> I got the data by extra logging but the issue is that it is always sending
> the same xmin. There are no long running transactions or inactive slots on
> the standby
>
> Since it is sending the same xmin, vacuum is not happening on primary.
> After we set hot_standby_feedback to 'off', the xmin becomes null and
> vacuum goes through. If we revert hot_standby_feedback to 'on' again, it
> will be stuck in the same xmin.
>
> We are unable to determine the transaction for xmin that is holding back
> the slots.
>
> Thanks,
> Nikhil
>
> On Sat, Jul 23, 2022 at 12:30 AM Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)com>
> wrote:
>
>> Hi,
>>
>> Is there a way we can get the actual messages(esp the xmin) that are sent
>> to the primary when hot_standby_feedback is enabled on standby.
>>
>> Thanks,
>> Nikhil
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Murthy Nunna | 2022-07-27 11:48:55 | RE: pg_upgrade failure upgrading from v10.8 to v14.4 |
Previous Message | Scott Ribe | 2022-07-26 21:51:07 | Re: Index is not a btree |