> On Jan 20, 2016, at 19:54, AI Rumman <[email protected]> wrote: > > But, will it not create transaction wraparound for those table? > > Thanks. > >> On Wed, Jan 20, 2016 at 4:44 PM, Melvin Davidson <[email protected]> >> wrote: >> >> ALTER TABLE your_schema.your_table SET (autovacuum_enabled = false, >> toast.autovacuum_enabled = false); >> >>> On Wed, Jan 20, 2016 at 6:22 PM, AI Rumman <[email protected]> wrote: >>> Hi, >>> >>> I have a table with daily partition schema on Postgresql 9.1 where we are >>> keeping 2 years of data. >>> Often I experience that autovacuum process is busy with old tables where >>> there is no change. How can I stop it? >>> Please advice. >>> I typically run a vacuum freeze in old partitions that don't get any changes as part of a maintenance script. If the tables actually get no changes, autovac should ignore them unless wrap becomes an issue at max_freeze_age... Which, it shouldn't of you vacuum freeze and there are no changes.
>>> Thanks. >> >> >> >> -- >> Melvin Davidson >> I reserve the right to fantasize. Whether or not you >> wish to share my fantasy is entirely up to you. >
