@kapa.ai airbyte 1.8.5 postgres destination does

select count(*)

from the table it just loaded. Can that be configured off?

Thinking completed Based on the provided knowledge sources, there is no setting or configuration option available to disable or toggle off this behavior [Github Issue (closed): destination-postgres (Direct Load)]. In versions using Direct Load (such as Bulk CDK implementations before

1.1.0

and connector versions up to

3.0.18

), the destination runs an unconditional

SELECT COUNT(*)

at startup/status-gathering via

BaseDirectLoadInitialStatusGatherer.getTableStatus()

simply to check whether the destination table is empty [Github Issue (closed): destination-postgres (Direct Load); feat(bulk-cdk): add tableIsEmpty]. Rather than a configuration toggle, this issue was resolved in the connector itself: • Airbyte upgraded the Bulk CDK to

1.1.0

and updated

destination-postgres

in version

3.0.19

[fix(destination-postgres): avoid full table counts]. • Starting in version

3.0.19

, the connector replaces the full

COUNT(*)

with an efficient

SELECT NOT EXISTS(SELECT 1 FROM <table> LIMIT 1)

check, which satisfies the emptiness query immediately without performing a full table scan [fix(destination-postgres): avoid full table counts]. To eliminate the performance overhead of full table scans, upgrade your

destination-postgres

connector to version

3.0.19

or higher. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.