Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Hi team! I’m receiving an error (and sync failure after initial was successful) in the logs that I didn’t find anywhere in the GitHub Issues.  The Postgres source with CDC configured is failing with an error `PSQLException: ERROR: publication "airbyte_publication" does not exist` Which doesn’t seem correct since few logs line above it was clear that Airbyte worker got a list of tables which are added to mentioned publication. Details in thread.

This is the error log entry
```2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.p.ChangeEventSourceCoordinator(streamEvents):173 - Starting streaming
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.c.p.PostgresStreamingChangeEventSource(execute):127 - Retrieved latest position from stored offset 'null'
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.c.p.c.WalPositionLocator(&lt;init&gt;):40 - Looking for WAL restart position for last commit LSN 'null' and last change LSN 'null'
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.c.p.c.PostgresReplicationConnection(initPublication):145 - Initializing PgOutput logical decoder publication
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.c.p.c.PostgresConnection(readReplicationSlotInfo):251 - Obtained valid replication slot ReplicationSlot [active=false, latestFlushedLsn=LSN{0/407E708}, catalogXmin=1932731695]
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.j.JdbcConnection(lambda$doClose$3):956 - Connection gracefully closed
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.u.Threads(threadFactory):270 - Requested thread factory for connector PostgresConnector, id = backend named = keep-alive
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.u.Threads$3(newThread):287 - Creating thread debezium-postgresconnector-backend-keep-alive
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.c.p.PostgresSchema(printReplicaIdentityInfo):103 - REPLICA IDENTITY for 'public.users' is 'DEFAULT'; UPDATE and DELETE events will contain previous values only for PK columns
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.c.p.PostgresSchema(printReplicaIdentityInfo):103 - REPLICA IDENTITY for 'public.devices' is 'DEFAULT'; UPDATE and DELETE events will contain previous values only for PK columns
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 INFO i.d.c.p.PostgresStreamingChangeEventSource(processMessages):202 - Processing messages
2022-08-19 08:29:27 source &gt; 2022-08-19 08:29:27 ERROR i.d.p.ErrorHandler(setProducerThrowable):35 - Producer failure
2022-08-19 08:29:27 source &gt; org.postgresql.util.PSQLException: ERROR: publication "airbyte_publication" does not exist
2022-08-19 08:29:27 source &gt;   Where: slot "airbyte_slot", output plugin "pgoutput", in the change callback, associated LSN 0/407E708
2022-08-19 08:29:27 source &gt; 	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2675) ~[postgresql-42.3.5.jar:42.3.5]
2022-08-19 08:29:27 source &gt; 	at org.postgresql.core.v3.QueryExecutorImpl.processCopyResults(QueryExecutorImpl.java:1263) ~[postgresql-42.3.5.jar:42.3.5]
...```


I think I’ve found explanation related to my problem
Will give it a try

<https://github.com/airbytehq/airbyte/pull/13949>

<https://airbytehq.slack.com/archives/C038KM9NF7Z/p1660827978680059> from yesterday too :slightly_smiling_face:

ah, blame on me, I don’t know how I missed that :smile: sorry, usually use search before asking the question