Mon Jan 6 11:15:50 PST 2014
- Previous message: [Slony1-general] Slony getting 'hung up' on an event?
- Next message: [Slony1-general] Slony getting 'hung up' on an event?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 01/06/14 13:51, Brian Fehrle wrote: > ... > > 2014-01-06 11:43:22 MST DEBUG1 remoteHelperThread_1_1: 112.859 seconds > delay for first row > 2014-01-06 11:43:22 MST DEBUG1 remoteHelperThread_1_1: 112.906 seconds > until close cursor > 2014-01-06 11:43:22 MST DEBUG1 remoteHelperThread_1_1: inserts=61 > updates=300 deletes=55 truncates=0 Almost 2 minutes to select 416 log rows? That looks wrong. Can you change the slon configuration to have an explain_interval? With that slon will emit EXPLAIN output for the log selection query in that interval. Maybe something is screwing up the optimizer. Jan -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin
- Previous message: [Slony1-general] Slony getting 'hung up' on an event?
- Next message: [Slony1-general] Slony getting 'hung up' on an event?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list