Mr. Pierce, others,
I spoke too soon on this. I'd like to do your alter database.. command
but it isn't working. I've tried:
postgres=# ALTER DATABASE ddev2 SET autovacuum = off;
both as 'postgres' user, and the ddev2 owner user (which has owner
privs), and I'm always getting this error:
ERROR: parameter "autovacuum" cannot be changed now
I've checked some documentation, tried many variations of the command,
(e.g. = off, false, 0, etc.) tried other variations as well. As you can
see in the above example, I'm connected to 'postgres' database. I tried
'ddev2' also, etc. The above error is *always* the response.
I'm certain that there are no other user sessions in this database.
So.. what are the magic words? Thanks again!
--
--o--o--o--o--o--o--o--o--o--o--o--o--
Jim Longwill
JLongwill@psmfc.org
--o--o--o--o--o--o--o--o--o--o--o--o--
On 10/29/2015 12:05 PM, John R Pierce wrote:
> On 10/29/2015 11:52 AM, Jim Longwill wrote:
>> I have a question about Postgres management. Our situation is
>> probably similar to many data shops.
>>
>> We have one (Linux) server, and one Postgres installation (v9.4),
>> hence one Postgres process-daemon set running on the server, but we
>> have multiple databases created: ddev1, ddev2, ddev3.
>>
>> 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;
>
>
>
