| From: | Jim Nasby <jim(at)nasby(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: truncating pg_multixact/members |
| Date: | 2014-01-07 00:50:42 |
| Message-ID: | 52CB4F62.3060902@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/4/14, 8:19 AM, Robert Haas wrote:
> Also, while multixactid_freeze_min_age should be low, perhaps a
> million as you suggest, multixactid_freeze_table_age should NOT be
> lowered to 3 million or anything like it. If you do that, people who
> are actually doing lots of row locking will start getting many more
> full-table scans. We want to avoid that at all cost. I'd probably
> make the default the same as for vacuum_freeze_table_age, so that
> mxids only cause extra full-table scans if they're being used more
> quickly than xids.
Same default as vacuum_freeze_table_age, or default TO vacuum_freeze_table_age? I'm thinking the latter makes more sense...
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2014-01-07 01:02:43 | Re: ERROR: missing chunk number 0 for toast value |
| Previous Message | Jim Nasby | 2014-01-07 00:40:44 | Re: [PATCH] Store Extension Options |