npgsql

Say you have three prepared NpgsqlCommands. Because they must be executed separatedly. But sometimes two or all three must be executed at once (well, one after the other). Is there a way to batch and reuse these previously prepared commands using a single roundtrip to the server? (goal is to minimize latency) Now I use a fourth command and semicolon separate a copy of the original three commands, and prepare this -- but I assume this will use more resources at the server, and more SQL parsing at the npgsql client. Npgsql supports batching through including several statements in your

I have the following PLINQ statement in a C# program: foreach (ArrestRecord arrest in from row in arrestQueue.AsParallel() select row) { Geocoder geocodeThis = new Geocoder(arrest); writeQueue.Enqueue(geocodeThis.Geocode()); Console.Out.WriteLine("Enqueued " + ++k); } Both arrestQueue and writeQueue are ConcurrentQueues . Nothing is running in parallel: While running, total CPU usage is about 30%, and this is with everything else running, too. I have 8 cores (Hyper-Threading on a Core i7 720QM with 4 physical cores), and 4 of the 8 cores have virtually no utilization at all. The rest run

I'm writing a service which will be connecting to a remote postgres server. I'm looking for a good way to determine which exceptions should be treated as transient (worth retrying), and how to define an appropriate policy for connecting to a remote database. The service is using Npgsql for the data access. The documentation says that Npgsql will throw a PostgresException for sql errors and an NpgsqlException for "server related issues". So far the best I have been able to come up with is to assume all exceptions that are not PostgresExceptions should be treated as possibly transient, worth

I try import data to postgresql table from file via npgsql BeginTextImport This is my code: public Object Copy(String sSchemaAndTableName, String sFilePath, Boolean bIsImport) { Boolean bRet = true; Object oResult = new Object(); NpgsqlConnection conn = new NpgsqlConnection(sConnectionString); NpgsqlCommand cmd = new NpgsqlCommand(); try { conn.Open(); NpgsqlTransaction transaction = conn.BeginTransaction(); if (File.Exists(sFilePath)) { try { if (bIsImport) { conn.BeginTextImport("COPY " + sSchemaAndTableName + " FROM '" + sFilePath + "';"); } else { conn.BeginTextExport("COPY " +

I'm using Postgresql on Windows in a C# application. The problem I'm having is really weird and can be described as follows: I restart my Windows I run the program One specific query fails: SELECT COUNT(*) AS c FROM files WHERE total_bytes IS NOT NULL I run the program again and everything works normally Weird notes: I tried making another query before that one (even using the same table) and it worked: SELECT COUNT(*) AS c FROM files I wasn't able to reproduce the error restarting Postgresql. It only happens on a Windows reboot. And it happens only once. The exception traceback: Npgsql