From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Coding help |
Date: | 2002-08-16 15:25:28 |
Message-ID: | 200208161125.28081.matthew@zeut.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Absolutely, I have been looking into this and I have some thoughts, but right
now all I was trying to do was some rough implementations just to help me
make sure I understand all / most of the issues. I am very new to hacking on
the guts of the backend.
I plan on posting a formal proposal when I feel more confident as to what I'm
talking about.
On Friday 16 August 2002 10:10 am, Jan Wieck wrote:
> "Matthew T. O'Connor" wrote:
> > Hello, I'm playing with creating an auto vacuum daemon, but it is my
> > first time inside the pg source code and I'm a bit lost.
> >
> > I have gotten as far as having a vacuum daemon created on postmaster
> > startup. It's just a fork from the postmaster, cribbed mostly from the
> > stat collector code.
>
> I recall that there has been discussion and so far the conclusion that
> an automatic vacuum daemon is not the solution everyone needs. If you
> really want to spend the effort on doing this, can we please see some
> proposal about possible configuration options, how the daemon decides
> what to vacuum when and the like?
>
>
> Jan
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2002-08-16 15:35:12 | Re: where to put NO_MKTIME_BEFORE_1970? |
Previous Message | Bruce Momjian | 2002-08-16 15:24:21 | Re: Open 7.3 issues |