| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Michael Chau <michael(dot)chau(at)gameyourgame(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Try to understand VACUUM and its settings |
| Date: | 2015-10-07 17:55:06 |
| Message-ID: | 56155C7A.5040907@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/5/15 5:00 PM, Michael Chau wrote:
> So, do I need to run vacuum freeze on those tables? Also, if
> autovacuum_freeze_max_age is commented, does it still mean that the
> default is 200M?
Yes, and unless you're running a very high transaction rate you probably
don't need to mess with it. Likewise you normally don't need to
explicitly freeze, though it's not a bad idea to do so after a large
data load. Just make sure that there's no open transactions that were
started before the data load transaction when you run the VACUUM.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-10-07 18:01:41 | Re: md5(large_object_id) |
| Previous Message | Jim Nasby | 2015-10-07 17:52:33 | Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type? |