It seems you are encountering a schema validation error related to the

timestamp without timezone

data type in your PostgreSQL source. This issue might be caused by the lack of timezone information in the timestamp value. One possible solution is to modify your custom connector to handle the

timestamp without timezone

data type properly. You can refer to this [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1665296557490639) where a user faced a similar issue and resolved it by updating the connector's logic. However, if you are not using a custom connector and still facing this issue, it might be helpful to open a GitHub issue in the [Airbyte repository](https://github.com/airbytehq/airbyte/issues) to report the problem and seek assistance from the Airbyte team. Keep in mind that the information provided here is based on the available extracts, and there might be other factors contributing to the issue that are not covered in these extracts.

If you are using a

timestamp without timezone

column in Postgres and facing issues with replication in Airbyte, you can consider changing the logic in the connector. Here's a previous conversation from Slack that might help you: > User: Thanks @Eli Sigal for the reply . I cannot go through the route for source table. How do i change the logic in the connector > > User: just change the code behind the scenes > > go to: > airbyte-integrations/connectors/source-postgres/src/main/java/io/airbyte/integrations/source/postgres You can modify the connector code to handle the

timestamp without timezone

column according to your requirements. However, please note that modifying the connector code might require some programming knowledge and understanding of the Airbyte connector structure. If you need more information, you can refer to the [Airbyte documentation](https://docs.airbyte.com) or ask for help in the [Airbyte community](https://airbytehq.slack.com).

It seems that you are facing issues with the

timestamp without timezone

column in Postgres when using it as a cursor field in Airbyte. The issue might not be directly related to the cursor field itself, but rather how the

timestamp without timezone

is being handled during replication. In a previous [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1665296557490639), a user faced a similar issue, and the suggested workaround was to modify the logic in the connector to handle the

timestamp without timezone

column properly. To modify the connector code, you can refer to the [Airbyte Postgres connector source code](https://github.com/airbytehq/airbyte/tree/master/airbyte-integrations/connectors/source-postgres/src/main/java/io/airbyte/integrations/source/postgres). Please note that modifying the connector code might require some programming knowledge and understanding of the Airbyte connector structure. If you need more information or assistance, you can refer to the [Airbyte documentation](https://docs.airbyte.com) or ask for help in the [Airbyte community](https://airbytehq.slack.com).