Optimal Transaction Size in Postgres?

Question

I am starting a process that makes many updates (> 100,000) for a table. I have a choice between posting all updates in one transaction or completing transactions every 1000 or so.

Ignore at the moment the case when the transaction ends with an error and is aborted. I am interested in the best transaction size for working with memory and speed.

Answer 1

Ignoring the case of a transaction failure, batching will use less memory.

, , , - , .