@kapa.ai i'm syncing data with a postgres connector. airbyte is running a

select count(*)

query before it starts fetching the data. is it possible to disable this?

Based on the information provided in the knowledge sources, there doesn't seem to be a direct way to disable the

SELECT COUNT(*)

query that Airbyte runs before fetching data from a Postgres source. However, I can provide some relevant context and potential workarounds: 1. The issue of performance during initial sync for large tables has been recognized. In [Github Issue #25368](https://github.com/airbytehq/airbyte/issues/25368), it's mentioned that for very large tables, the initial incremental sync can take a long time and potentially time out before starting to emit records. 2. While this issue doesn't specifically mention the

SELECT COUNT(*)

query, it does discuss potential optimizations for large table syncs. The proposed solution involves changing the initial incremental sync query to include ranges, which could potentially improve performance. 3. There's also a mention of advanced configuration options for the Postgres source in the [Airbyte documentation](https://docs.airbyte.com/integrations/sources/postgres#advanced-configuration), but the link provided in the knowledge sources doesn't contain specific information about disabling the count query. 4. In [Github Issue #9501](https://github.com/airbytehq/airbyte/issues/9501) (referenced in a forum post), there was discussion about adding the ability to set additional parameters for the Postgres source. While this doesn't directly address your question, it suggests that Airbyte is working on providing more configuration options for the Postgres source. Given the available information, it appears that there isn't a straightforward way to disable the

SELECT COUNT(*)

query at the moment. If this is causing significant performance issues, you might want to consider: 1. Checking for any updates to the Postgres source connector that might include performance optimizations. 2. Exploring the advanced configuration options, if available, to see if there are any settings that could help mitigate the performance impact. 3. If the issue is severe, you may want to raise it as a feature request or performance improvement suggestion in the Airbyte GitHub repository or community forums. Remember, Airbyte is actively developing and improving their connectors, so it's worth keeping an eye on updates that might address this issue in the future.

@kapa.ai what does the

cursor_record_count

parameter in the connection state do?

A message from kapa.ai

New message text here