Use execute_values instead of execute_batch for better bulk insert performance with PostgresHook#68207
Merged
Merged
Conversation
… insert performance with psycopg2 in insert_rows of PostgresHook when fast_executemany is enabled unless psycopg3 is used
eladkal
approved these changes
Jun 8, 2026
…ycopg3 is being used as this has no effect
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR optimizes
PostgresHook.insert_rows()whenfast_executemany=Trueby switching fromexecute_batchtoexecute_valuesfor psycopg2, which provides significantly better bulk insert performance.Changes
psycopg2 with
fast_executemany=True: Now usespsycopg2.extras.execute_values()instead ofexecute_batch(). This batches all rows into a singleINSERTstatement with multiple value tuples, reducing round-trips and improving throughput.psycopg3: Falls back to the default
DbApiHook.insert_rows()implementation. psycopg3's nativeexecutemanyalready uses pipelining internally, so there's no benefit to a custom implementation—andexecute_valuesis not compatible with psycopg3.Format string handling: Both code paths now explicitly set
_insert_statement_formatto ensure correct SQL generation and self-healing if a previous call failed mid-execution.Why execute_values over execute_batch?
execute_batchINSERTstatements in batchesexecute_valuesINSERT ... VALUES (...), (...), (...)statementexecute_valuesis typically 2-3x faster for bulk inserts because it minimizes statement parsing overhead and network round-trips.Testing
execute_valuesis called instead ofexecute_batchfast_executemany=TrueWas generative AI tooling used to co-author this PR?
Claude Opus 4.6
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.