Re: [GENERAL] Question about optimizing access to a table.

2013-12-11 Thread Jeff Janes
On Wed, Dec 11, 2013 at 1:49 AM, Herouth Maoz wrote: > > On 10/12/2013, at 20:55, Jeff Janes wrote: > > > On Tue, Dec 10, 2013 at 8:23 AM, Herouth Maoz wrote: > >> >> Hello. >> >> I have one particular table with very specialized use. I am sending >> messages to some partner. The partner processe

Re: [GENERAL] Question about optimizing access to a table.

2013-12-11 Thread Kevin Grittner
Herouth Maoz wrote: > On 10/12/2013, at 20:55, Kevin Grittner wrote: >> First, make sure that you are on the latest minor release of >> whatever major release you are running.  There were some serious >> problems with autovacuum's table truncation when a table was >> used as a queue and size fluc

Re: [GENERAL] Question about optimizing access to a table.

2013-12-11 Thread Herouth Maoz
On 10/12/2013, at 20:55, Kevin Grittner wrote: > Herouth Maoz wrote: > >> The problem starts when our partner has some glitch, under high >> load, and fails to send back a few hundred thousand reports. In >> that case, the table grows to a few hundred records, and they are >> not deleted until

Re: [GENERAL] Question about optimizing access to a table.

2013-12-11 Thread Herouth Maoz
On 10/12/2013, at 20:55, Jeff Janes wrote: > > On Tue, Dec 10, 2013 at 8:23 AM, Herouth Maoz wrote: > > Hello. > > I have one particular table with very specialized use. I am sending messages > to some partner. The partner processes them asynchronously, and then returns > the status report

Re: [GENERAL] Question about optimizing access to a table.

2013-12-10 Thread Jeff Janes
On Tue, Dec 10, 2013 at 8:23 AM, Herouth Maoz wrote: > > Hello. > > I have one particular table with very specialized use. I am sending > messages to some partner. The partner processes them asynchronously, and > then returns the status report to me. The table is used to store a > serialized vers

Re: [GENERAL] Question about optimizing access to a table.

2013-12-10 Thread Kevin Grittner
Herouth Maoz wrote: > The problem starts when our partner has some glitch, under high > load, and fails to send back a few hundred thousand reports. In > that case, the table grows to a few hundred records, and they are > not deleted until they hit their expiry date, at which point the > "garbage