Postgres Pro
Downloads
Home   >   mailing lists

RE: [EXTERNAL] Re: Inserts and bad performance - Mailing list pgsql-general

From Godfrin, Philippe E
Subject RE: [EXTERNAL] Re: Inserts and bad performance
Date
Msg-id SA0PR15MB3933644C28286B9BEC3B218C82619@SA0PR15MB3933.namprd15.prod.outlook.com
Whole thread Raw
In response to Re: Inserts and bad performance  (Gavin Roy <gavinr@aweber.com>)
Responses Re: [EXTERNAL] Re: Inserts and bad performance  (Michael Lewis <mlewis@entrata.com>)
Re: RE: [EXTERNAL] Re: Inserts and bad performance  (Ali . <mp.x@bk.ru>)
List pgsql-general
Tree view

The notion of COPY blocks and asynchronously is very interesting

 

From: Gavin Roy <gavinr@aweber.com>
Sent: Wednesday, November 24, 2021 1:50 PM
To: Godfrin, Philippe E <Philippe.Godfrin@nov.com>
Cc: pgsql-general@lists.postgresql.org
Subject: [EXTERNAL] Re: Inserts and bad performance

 

 

 

 

On Wed, Nov 24, 2021 at 2:15 PM Godfrin, Philippe E <Philippe.Godfrin@nov.com> wrote:

Greetings

I am inserting a large number of rows, 5,10, 15 million. The python code commits every 5000 inserts. The table has partitioned children.

 

On the Python client side, if you're using psycopg, you should consider using using COPY instead of INSERT if you're not:

 

 

And if using psycopg2, execute_batch might be of value:

 

 

Regards,

 

Gavin

 

 

pgsql-general by date:

Previous
From: "Godfrin, Philippe E"
Date:
Subject: RE: [EXTERNAL] Re: Inserts and bad performance
Next
From: Michael Lewis
Date:
Subject: Re: [EXTERNAL] Re: Inserts and bad performance