| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Bruno Wolff III <bruno(at)wolff(dot)to>, 225680(at)bugs(dot)debian(dot)org, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Fwd: Default pg_autovacuum config glitches |
| Date: | 2004-03-27 19:19:17 |
| Message-ID: | 20040327111457.C2823@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, 27 Mar 2004, Tom Lane wrote:
> Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
> > The postmaster's seems to have a section that does a null device open,
> > dup2s and a close at the end of pmdaemonize in the 7.4 and 7.5 versions on
> > my box:
>
> Yes, and that behavior is exactly why we deprecate -S ... I don't think
> that the autovacuum daemon should emulate it.
Oh, I totally agree with that, but wanted to point it out since there
seemed to be a question in terms of what the postmaster did in the code
that was cribbed for the autovacuum daemon.
> This is all moot though since we seem to have a consensus that the
> autovac daemon will become a postmaster child in 7.5. There is
> therefore no reason for it to worry about daemonizing itself.
True, but I sort of inferred that the debian bug was also aimed towards
later 7.4 releases.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PostgreSQL Bugs List | 2004-03-28 03:24:08 | BUG #1118: Misleading Commit message |
| Previous Message | Tom Lane | 2004-03-27 18:35:37 | Re: Fwd: Default pg_autovacuum config glitches |