Re: Reindex doesn’t not working replica nodes

Thanks for sharing the additional information. Initially, the query didn't
provide the full context regarding OS compatibility, which is crucial in
understanding the replication issues (physical and logical).
For future inquiries, including details like OS versions, replication
setups, and any specific configurations can help us address your concerns
more accurately and efficiently.

On Fri, Aug 16, 2024 at 5:19 PM Mohammed Afsar <vmdapsar(at)gmail(dot)com> wrote:

> Thanks for the information but we are encountered OS compatibility issues
> source to replica servers.
>
> Source Alma Linux 9.0
> Replica centos 7.0
> Patroni 3.1.0
>
> Regards,
> Mohammed Afsar
>
>
> On Fri, 16 Aug 2024 at 4:50 PM, khan Affan <bawag773(at)gmail(dot)com> wrote:
>
>> Hi Mohammed,
>>
>> PostgreSQL replication is based on replicating WAL (Write-Ahead Log)
>> records, which capture changes to data files such as inserts, updates,
>> deletes, and the creation of new tables. However,
>>
>> WAL does not include the physical structure of indexes.
>>
>> If you're encountering issues like zero rows being fetched from the
>> replica, it could be due to index inconsistencies or replication lag. To
>> ensure your read replica has updated indexes, you can promote the replica
>> to be the primary node, perform the REINDEX operation, and then revert the
>> roles, making the original primary node the primary again.
>>
>> Regards
>> Muhammad Affan
>>
>> On Wed, Aug 14, 2024 at 5:58 PM Mohammed Afsar <vmdapsar(at)gmail(dot)com>
>> wrote:
>>
>>> Dear experts,
>>>
>>>
>>> We have initiated reindex on source db but it not replicated to replica
>>> db and we have having select query fetching with zero rows but data exiting
>>> on the table.
>>> Postgres 11.10 streaming replication
>>>
>>> Regards,
>>> Mohammed Afsar
>>>
>>