Tomasz Rakowski wrote:
I see autovacuum process starting in avarage every 5 minutes
(table contains 30.000 records, and update rate is about 1000records /min).
But what is strange is that the number of pages allocated to the table
are constant (at least for this hour: 500)
and number of pa
Devrim GUNDUZ wrote:
On Wed, 2006-12-06 at 23:32 -0800, [EMAIL PROTECTED] wrote:
I got installed on my windows box and my debian box. But is there a way
to install 8.2 on centos 4 using yum?
I am about to create a yum repo for PGDG RPM sets. Clodoaldo Pinto Neto
sent me the instructions o
Csaba Nagy wrote:
On Fri, 2006-12-08 at 17:39, Bernhard Weisshuhn wrote:
On Fri, Dec 08, 2006 at 05:26:22PM +0100, Harald Armin Massa <[EMAIL
PROTECTED]> wrote:
Now we just need fast, stable and native replication for " The Girl
That Every Man Secretly Wishes He Was Married To!"
I want repli
Magnus Hagander wrote:
But seriously, I'm definitly interested in ways it can be improved - and
that's true of the whole web team, I'm sure. It was just my way of
saying "it will take a while", but I'll file it away as a good thing to
do when there is a moment of spare time.
I like the way the
Magnus Hagander wrote:
We still have a searchform at search.postgresql.org. To search
mainliglists, click Archives search. You can select a list, or a group
of list, there. Or just search them all.
Anyone see any value in allowing the mailing list search to be sorted by
both ascending and desc
Alvaro Herrera wrote:
Csaba Nagy wrote:
Alternatively, perhaps a threshold so that a table is only considered
for vacuum if:
(table-size * overall-activity-in-last-hour) < threshold
Ideally you'd define your units appropriately so that you could just
define threshold in postgresql.conf as 3
Bruce Momjian wrote:
Yes, I think there are these TODO items. I was waiting to see what
additional replies there are before adding them.
Speaking of which, I was just looking at the TODO at:
http://www.postgresql.org/docs/faqs.TODO.html
and I think this item:
* Improve xid wraparound detect
Glen Parker wrote:
Tom Lane wrote:
What is it that you find inadequate
about regular autovacuum? It is configurable through the pg_autovacuum
catalog --- which I'd be the first to agree is a sucky user interface,
but we're not going to set the user interface in concrete until we are
pretty conf
Glen Parker wrote:
If it isn't there somewhere already, I would ask to add:
4) Expose all information used by autovacuum to form its decisions.
You could argue that this is already there, although not easy to get at
I suppose. But all table threshold settings are available either in the
pg_
Alvaro Herrera wrote:
Matthew O'Connor wrote:
Glen Parker wrote:
5) Expose a very easy way to discover autovacuum's opinion about a
particular table, for example "table_needs_vacuum(oid)", ignoring any
time constraints that may be in place.
This might be a nice feature how
Glen Parker wrote:
Erik Jones wrote:
Matthew O'Connor wrote:
Glen Parker wrote:
If it isn't there somewhere already, I would ask to add:
Expose a very easy way to discover autovacuum's opinion about a
particular table, for example "table_needs_vacuum(oid)", ignor
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matthew
O'Connor
Sent: Tuesday, December 19, 2006 5:37 PM
To: Glen Parker
Cc: Postgres general mailing list
Subject: Re: [GENERAL] Autovacuum Improvements
Glen Parker wrote:
Erik Jones wrote:
Matthew O'Connor
Glen Parker wrote:
Matthew O'Connor wrote:
No, how dirty a table isn't subjective, what is subjective is the
question "Does it need to be vacuumed?". A that is 1% dirty (to use
your term) probably doesn't *need* to be vacuumed, but you might
choose to vacuum it any
Glen Parker wrote:
I wonder if the simple solution is to just have a cron script modify
postgresql.conf and pg_ctl reload. That seems very flexible, or have
two postgresql.conf files and move them into place via cron.
I'd still prefer to vacuum on demand actually. Rather than hope that
autov
Alvaro Herrera wrote:
Glen Parker wrote:
That really seems like something that, if it's powerful, would also be
very complicated. If the autovacuum system could just call a user
defined function, all the complexity could be dropped back into the
admin's lap (which is fine with me :-).
I hav
15 matches
Mail list logo
