From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Configure Different Databases on One Server |
Date: | 2015-10-29 19:14:32 |
Message-ID: | 3572.1446146072@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
John R Pierce <pierce(at)hogranch(dot)com> writes:
> On 10/29/2015 11:52 AM, Jim Longwill wrote:
>> I would like to do a different vacuum configuration on ddev2 than on
>> ddev1, such as turning off autovacuum, etc. How do I do this? E.g.
>> how do I turn off autovacuum on one database .. using different
>> postgres.conf files(?) or within the database, without affecting the
>> other database(s) on the same localhost?
>> Is there a relatively easy way to do this?
> alter database dbname set autovacuum = false;
Might be trickier than it looks though. I think individual autovacuum
worker processes will pick up such settings, but the launcher will not
since it doesn't ever attach to any individual database. So a lot of
undocumented implementation details would matter as to where particular
settings get used ...
Might be better to settle for configuring specific large tables using
per-table vacuum settings, and not sweat the small stuff at a per-DB
level.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2015-10-29 19:27:06 | Re: Domain check constraint not honored? |
Previous Message | Dane Foster | 2015-10-29 19:10:23 | Re: mysql_fdw trouble |