From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
---|---|
To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_autovacuum next steps |
Date: | 2004-03-23 00:42:39 |
Message-ID: | 405F87FF.7010209@zeut.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gavin Sherry wrote:
>I was initially against the idea of using libpq but its growing on me too.
>
>I think it would be good if the core functions of pg_autovacuum: threshold
>algorithms, connection, issuing commands can be (re?)designed such that
>not only the backend can link against it but also a stripped down
>pg_autovacuum binary which can be used manually. That way users can have a
>choice and a workaround if there are any issues with the backend model.
>Also useful for debugging.
>
I agree. Initially, it appears that this won't be a problem since the
pg_autovacuum executable will be untouched (or as untouched as possible
anyway), it will just be launched by the backend. Going forward if I
use any of the functionality provided by the backend (error reporting
etc...) I will then have to deign it to work in both stand alone and
postmaster sub-process modes, which I think is doable.
Matthew
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2004-03-23 00:49:34 | Re: pg_autovacuum next steps |
Previous Message | Bruce Momjian | 2004-03-23 00:04:26 | Re: [HACKERS] listening addresses |