Re: [PERFORM] Impact of track_activity_query_size on high traffic OLTP system

I always bump it up, but usually just to 4096, because I often have queries that are longer than 1024 and I'd like to be able to see the full query. I've never seen any significant memory impact. I suppose if you had thousands of concurrent queries it would add up, but if you only have a few

[PERFORM] Impact of track_activity_query_size on high traffic OLTP system

I have found some examples of people tweaking this parameter track_activity_query_size to various setting such as 4000, 1, 15000, but little discussion as to performance impact on memory usage. What I don't have a good sense of is how significant this would be for a high traffic system with

[PERFORM] Postgresql, and ODBC handles

Summary: I am facing a contention problem with ODBC on the client side. strace and perf top show we are serializing over what appears to be accesses to the ODBC statement handle. Contention goes down if I use multiple processes instead of multiple threads within a process. Also, all the threads

Re: [PERFORM] Hi

> From: Daulat Ram > To: "pgsql-performance@postgresql.org" > Sent: Thursday, 13 April 2017, 7:25 > Subject: [PERFORM] Hi > > Hello, > > I need to know the criteria behind for settings the work_mem in PostgreSQL, > please give the

[PERFORM] Hi

Hello, I need to know the criteria behind for settings the work_mem in PostgreSQL, please give the example also if possible. Regards, Daulat