I keep getting this error when writing data

2024-05-26 15:46:25 2024-05-26 12:46:25.746 UTC [27] LOG:  checkpoint starting: wal
2024-05-26 15:47:14 2024-05-26 12:47:14.763 UTC [27] LOG:  could not open file "pg_wal/": No such file or directory
2024-05-26 15:47:14 2024-05-26 12:47:14.763 UTC [27] LOG:  could not remove file "pg_wal/": No such file or directory

It looks like you are encountering an issue related to the write-ahead logs (WAL) in your Postgres source. This can happen when the WAL files needed for incremental syncs are removed by Postgres. Here are some steps you can take to address this issue: 1. Sync the data source more frequently: This can help ensure that the WAL files are read before they are purged or archived by Postgres. 2. Set a higher

wal_keep_size

: This parameter controls the amount of WAL files that Postgres retains. Increasing this value can help prevent the WAL files from being removed too quickly. Note that this will require more disk space. You can find more details on how to configure

wal_keep_size

in the [Postgres documentation](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-WAL-KEEP-SIZE). Here is the relevant log message you might see when this issue occurs:

Saved offset is before Replication slot's confirmed_flush_lsn, Airbyte will trigger sync from scratch

For more detailed troubleshooting steps, you can refer to the [Airbyte documentation on Postgres troubleshooting](https://docs.airbyte.com/integrations/sources/postgres/postgres-troubleshooting#under-cdc-incremental-mode-there-are-still-full-refresh-syncs). If you continue to experience issues, please provide more details or check the Airbyte community forums for additional support. Sources: - [Postgres Troubleshooting](https://docs.airbyte.com/integrations/sources/postgres/postgres-troubleshooting#under-cdc-incremental-mode-there-are-still-full-refresh-syncs)