On Wed, Jan 20, 2016 at 6:00 PM, Scott Mead wrote:
>
>
> On Jan 20, 2016, at 19:54, AI Rumman wrote:
>
> But, will it not create transaction wraparound for those table?
>
> Thanks.
>
> On Wed, Jan 20, 2016 at 4:44 PM, Melvin Davidson
> wrote:
>
>>
>> ALTER TABLE your_schema.your_table SET (auto
> On Jan 20, 2016, at 19:54, AI Rumman wrote:
>
> But, will it not create transaction wraparound for those table?
>
> Thanks.
>
>> On Wed, Jan 20, 2016 at 4:44 PM, Melvin Davidson
>> wrote:
>>
>> ALTER TABLE your_schema.your_table SET (autovacuum_enabled = false,
>> toast.autovacuum_enabl
On 01/20/2016 04:54 PM, AI Rumman wrote:
But, will it not create transaction wraparound for those table?
See below for complete details:
http://www.postgresql.org/docs/9.1/interactive/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND
but short version from above:
23.1.4. Preventing Transaction I
You can only get a transaction wraparound if you actually do transactions
(insert/update/delete) on a table.
Since YOU claim you are not doing that, then you should not get a
transaction wraparound for that table.
On Wed, Jan 20, 2016 at 7:54 PM, AI Rumman wrote:
> But, will it not create trans
But, will it not create transaction wraparound for those table?
Thanks.
On Wed, Jan 20, 2016 at 4:44 PM, Melvin Davidson
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 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 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 autova
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.
Thanks.
