Re: broken reading on standby (PostgreSQL 16.2)

2024-04-25 Thread Pavel Stehule
čt 25. 4. 2024 v 12:53 odesílatel Melanie Plageman < melanieplage...@gmail.com> napsal: > On Thu, Apr 25, 2024 at 2:13 AM Pavel Stehule > wrote: > > > > Hi > > > > yesterday, I had to fix strange issue on standby server > > > > The query to freshly updated data fails > > > > select * from seller_

Re: broken reading on standby (PostgreSQL 16.2)

2024-04-25 Thread Melanie Plageman
On Thu, Apr 25, 2024 at 2:13 AM Pavel Stehule wrote: > > Hi > > yesterday, I had to fix strange issue on standby server > > The query to freshly updated data fails > > select * from seller_success_rate where create_time::date = '2024-04-23'; > ERROR: 58P01: could not access status of transaction

Re: broken reading on standby (PostgreSQL 16.2)

2024-04-25 Thread Pavel Stehule
čt 25. 4. 2024 v 10:52 odesílatel Andrey M. Borodin napsal: > > > > On 25 Apr 2024, at 12:06, Pavel Stehule wrote: > > > > Unfortunately, I have not direct access to backup, so I am not able to > test it. But VACUUM FREEZE DISABLE_PAGE_SKIPPING on master didn't help > > > > If Primary considers

Re: broken reading on standby (PostgreSQL 16.2)

2024-04-25 Thread Andrey M. Borodin
> On 25 Apr 2024, at 12:06, Pavel Stehule wrote: > > Unfortunately, I have not direct access to backup, so I am not able to test > it. But VACUUM FREEZE DISABLE_PAGE_SKIPPING on master didn't help > If Primary considers all freezable tuples frozen, but a standby does not, "disable page ski

Re: broken reading on standby (PostgreSQL 16.2)

2024-04-25 Thread Pavel Stehule
čt 25. 4. 2024 v 8:52 odesílatel Andrey M. Borodin napsal: > > > > On 25 Apr 2024, at 11:12, Pavel Stehule wrote: > > > > yesterday, I had to fix strange issue on standby server > > It’s not just broken reading, if this standby is promoted in HA cluster - > this would lead to data loss. > Recent

Re: broken reading on standby (PostgreSQL 16.2)

2024-04-24 Thread Andrey M. Borodin
> On 25 Apr 2024, at 11:12, Pavel Stehule wrote: > > yesterday, I had to fix strange issue on standby server It’s not just broken reading, if this standby is promoted in HA cluster - this would lead to data loss. Recently I’ve observed some lost heap updates ofter OOM-ing cluster on 14.11.

broken reading on standby (PostgreSQL 16.2)

2024-04-24 Thread Pavel Stehule
Hi yesterday, I had to fix strange issue on standby server The query to freshly updated data fails select * from seller_success_rate where create_time::date = '2024-04-23'; ERROR: 58P01: could not access status of transaction 1393466389 DETAIL: Could not open file "pg_xact/0530": No such file