Re: Index speeds up one row table (why)?

Rod Taylor wrote:

 >An 8 k page will hold approx 140 tuples based on your structure. So,
 >for every ~100 updates you'll want to run vacuum (regular, not full) on
 >the table

Alas, for this application, that means a vacuum once every 5 seconds or
so. I'll see if I can set up a separate little task to do that (I assume
at this rate, its better to just keep a connection open, than
setup/teardown). I don't suppose there is a way to get a trigger to do a
vacuum (which doesn't want to be in a transaction) (thinking it could
check for id mod 100=0 or something)? I also assume a few pages isn't
going to be that bad (just don't let it get to 11000 8).