Search Postgresql Archives

Re: Vacuum Full - Questions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Vacuum Full - Questions
From: Adam Brusselback <adambrusselback@xxxxxxxxx>
Date: Wed, 31 Aug 2016 19:24:05 -0400
In-reply-to: <CAJNY3itdjFCr7v-uLUO=yHWj3A4L8TLFA=rtaF+wby7U0LSv5A@mail.gmail.com>
References: <CAJNY3itdjFCr7v-uLUO=yHWj3A4L8TLFA=rtaF+wby7U0LSv5A@mail.gmail.com>

Yes that very well could happen because the size of the table changed, as well as stats being more accurate now. Just because you have a seq scan doesn't mean the planer is making a bad choice.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Vacuum Full - Questions
  - From: Patrick B

Prev by Date: Re: Clustered index to preserve data locality in a multitenant application?
Next by Date: Re: Vacuum Full - Questions
Previous by thread: Vacuum Full - Questions
Next by thread: Re: Vacuum Full - Questions
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux