PostgreSQL Query and/or Session CPU Usage

ADO.NET (used in the code sample) obviously communicates via network - even if a local Postgres instance is used. Using STDIN therefore results in quite a bit overhead. Before Postgres is able to insert the bulk data, it needs to be:

• serialized by C# client
• transmitted via network connection (in my case to localhost)
• deserialized by Postgres

This basically explains/justifies the described behaviour.

If the C# Client and Postgres are run on the same computer, you can speed up bulk inseration by writing a csv file on a local ssd drive (even better a ram drive) and execute the SQL statement 'Copy MyTable From x:\test.csv'.

Is there a way to mark the LISTEN-statement or this session as "unimportant"?

Unimportant to you? Perhaps.

Unimportant to Postgres? No.

Every connection is as "important" as every other.

If you want to kill off an active connection, look to the pg_cancel_backend function.