From: Dave E Martin XXIII <postgresql-to.dave@dave.to>
To: pgsql-bugs@postgresql.org
Subject: Re: Index speeds up one row table (why)?
Date: Sun, 01 Jun 2003 01:20:03 -0600
Message-ID: <3ED9A923.90500@dave.to> (raw)
References: <3ED93338.80806@dave.to>
<1054434573.11968.42.camel@jester>
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).
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: postgresql-to.dave@dave.to, pgsql-bugs@postgresql.org
Subject: Re: Index speeds up one row table (why)?
In-Reply-To: <3ED9A923.90500@dave.to>
References: <3ED93338.80806@dave.to> <1054434573.11968.42.camel@jester> <3ED9A923.90500@dave.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox