| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reviewing freeze map code |
| Date: | 2016-07-01 20:42:22 |
| Message-ID: | c954f72f-6900-346e-d2fc-e9a7a3d0efcf@BlueTreble.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/1/16 2:23 PM, Andres Freund wrote:
>> > The only
>> > cost of that is that vacuum will come along and mark the page
>> > all-visible again instead of skipping it, but that's probably not an
>> > enormous expense in most cases.
> I think the main cost is not having the page marked as all-visible for
> index-only purposes. If it's an insert mostly table, it can be a long
> while till vacuum comes around.
ISTM that's something that should be addressed anyway (and separately), no?
--
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
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-07-01 20:43:29 | Re: Reviewing freeze map code |
| Previous Message | Jim Nasby | 2016-07-01 20:34:58 | Re: Bad behavior from plpython 'return []' |