From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
Cc: | Russell Smith <mr-russ(at)pws(dot)com(dot)au>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Autovacuum in the backend |
Date: | 2005-06-17 13:54:52 |
Message-ID: | 20092.1119016492@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
"Matthew T. O'Connor" <matthew(at)zeut(dot)net> writes:
> ... People just didn't like including libpq
> into the backend for reasons I don't remember.
One reason I can think of is that there would be global-symbol conflicts
--- libpq has copies of some backend routines, but they are not
identical.
In any case, the argument that's being made here is that an integrated
autovac would be simple and newbie-friendly. I think it's impossible
for a libpq-using autovac to ever be invisible to the DBA, if only
because he has to configure it with an appropriate username/password,
make sure pg_hba.conf will actually let it into every database, etc.
There are way too many foot-guns in that scenario for my taste.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-17 13:57:33 | Re: Backing up multiple databases |
Previous Message | Együd Csaba | 2005-06-17 13:53:00 | Re: Making the DB secure |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-17 14:09:10 | Re: Utility database (Was: RE: Autovacuum in the backend) |
Previous Message | Bruce Momjian | 2005-06-17 13:42:43 | Re: Escape handling in strings |