RE: Time delayed LR (WAS Re: logical replication restrictions) - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: Time delayed LR (WAS Re: logical replication restrictions)
Date
Msg-id TYAPR01MB58662BA30277F63E8A83BAEBF5ED9@TYAPR01MB5866.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: Time delayed LR (WAS Re: logical replication restrictions)  ("Takamichi Osumi (Fujitsu)" <osumi.takamichi@fujitsu.com>)
List pgsql-hackers
Hi hackers,

> On Thursday, December 22, 2022 3:02 PM Takamichi Osumi (Fujitsu)
> <osumi.takamichi@fujitsu.com> wrote:
> > Attached the updated patch.
> > Again, I used one basic patch in another thread to wake up logical replication
> > worker shared in [2] for TAP tests.
> The v11 caused a cfbot failure in [1]. But, failed tests looked irrelevant
> to the feature to me at present.
> 
> While waiting for another test execution of cfbot, I'd like to check the detailed
> reason
> and update the patch if necessary.

I have investigated the failure and it seemed that it has been caused by VACUUM FREEZE.
Followings were copied from the server log.

```
2022-12-23 08:50:20.175 UTC [34653][postmaster] LOG:  server process (PID 37171) was terminated by signal 6: Abort
trap
2022-12-23 08:50:20.175 UTC [34653][postmaster] DETAIL:  Failed process was running: VACUUM FREEZE tab_freeze;
2022-12-23 08:50:20.175 UTC [34653][postmaster] LOG:  terminating any other active server processes
```

Same error has been raised in other threads [1], so we have concluded that this is not related with the patch.
The report was raised in another thread [2].

[1]: https://cirrus-ci.com/task/5630405437554688
[2]:
https://www.postgresql.org/message-id/TYAPR01MB5866B24104FD80B5D7E65C3EF5ED9%40TYAPR01MB5866.jpnprd01.prod.outlook.com


Best Regards,
Hayato Kuroda
FUJITSU LIMITED


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Allow placeholders in ALTER ROLE w/o superuser
Next
From: Richard Guo
Date:
Subject: Re: An oversight in ExecInitAgg for grouping sets