| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | amit(dot)kapila16(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: WAL segments removed from primary despite the fact that logical replication slot needs it. |
| Date: | 2022-10-17 09:14:32 |
| Message-ID: | Y00c+IlaWSHGNbnz@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Oct 17, 2022 at 03:53:07PM +0900, Kyotaro Horiguchi wrote:
> Anyway, I didn't come up with a possibility other than of someone else
> having removed those files.. For example, virus scan softwares. If
> any such software kills processes that is grabbing the files that the
> software identified as malicious and is going to remove, that could be
> happen?
We don't use virus scanning there. The pg12 server is on ubuntu 18.04,
used for normal production workload, and pg14 is on ubuntu focal, with
no load, aside from 2 physical streaming replication to pg14 replicas.
Best regards,
depesz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-10-17 12:03:15 | BUG #17646: create rule named "_RETURN" will cause pg core |
| Previous Message | hubert depesz lubaczewski | 2022-10-17 09:13:11 | Re: WAL segments removed from primary despite the fact that logical replication slot needs it. |