Re: [GENERAL] high transaction rate

2016-12-07 Thread Rob Sargent
On 12/07/2016 03:32 PM, John R Pierce wrote: On 12/7/2016 2:23 PM, Rob Sargent wrote: How does your reply change, if at all, if: - Fields not index - 5000 hot records per 100K records (millions of records total) - A dozen machines writing 1 update per 10 seconds (one machine writing every

Re: [GENERAL] high transaction rate

2016-12-07 Thread John R Pierce
On 12/7/2016 2:23 PM, Rob Sargent wrote: How does your reply change, if at all, if: - Fields not index - 5000 hot records per 100K records (millions of records total) - A dozen machines writing 1 update per 10 seconds (one machine writing every 2 mins) - - each to a different "5000" or (t

Re: [GENERAL] high transaction rate

2016-12-07 Thread Rob Sargent
On 12/07/2016 09:58 AM, John R Pierce wrote: On 12/7/2016 8:47 AM, Rob Sargent wrote: Please tell me that in this case, updating 2 (big)integer columns does not generate dead tuples (i.e. does not involve a insert/delete pair). if the fields being updated aren't indexed, and there's free tup

Re: [GENERAL] high transaction rate

2016-12-07 Thread John R Pierce
On 12/7/2016 8:47 AM, Rob Sargent wrote: Please tell me that in this case, updating 2 (big)integer columns does not generate dead tuples (i.e. does not involve a insert/delete pair). if the fields being updated aren't indexed, and there's free tuple space that has already been vacuumed in the

Re: [GENERAL] high transaction rate

2016-12-07 Thread Rob Sargent
2. Accumulation of dead tuples leading to what should be very short operations taking longer. No idea of that is helpful but where I would probably start Please tell me that in this case, updating 2 (big)integer columns does not generate dead tuples (i.e. does not involve a insert/delete pa

Re: [GENERAL] high transaction rate

2016-12-07 Thread Torsten Förtsch
Think I found it. classid 1262 is pg_database and I seem to remember that NOTIFY takes that lock. I dropped pg_notify from my function and got immediately >3500 tx/sec. On Wed, Dec 7, 2016 at 11:31 AM, Torsten Förtsch wrote: > On Wed, Dec 7, 2016 at 11:21 AM, Torsten Förtsch > wrote: > >> Hi, >

Re: [GENERAL] high transaction rate

2016-12-07 Thread Chris Travers
On Wed, Dec 7, 2016 at 11:31 AM, Torsten Förtsch wrote: > On Wed, Dec 7, 2016 at 11:21 AM, Torsten Förtsch > wrote: > >> Hi, >> >> I need to tune my database for a high update rate of a single small >> table. A little simplified it looks like this: >> >> CREATE TABLE temp_agg( >> topic TEXT PR

Re: [GENERAL] high transaction rate

2016-12-07 Thread Torsten Förtsch
On Wed, Dec 7, 2016 at 11:21 AM, Torsten Förtsch wrote: > Hi, > > I need to tune my database for a high update rate of a single small table. > A little simplified it looks like this: > > CREATE TABLE temp_agg( > topic TEXT PRIMARY KEY, > tstmp TIMESTAMP, > cnt BIGINT, > sum NUMERIC > ) >