| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Pre-set Hint bits/VACUUM FREEZE on data load..? |
| Date: | 2011-03-24 21:51:13 |
| Message-ID: | 20110324215113.GI4116@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> Also, you're not really going to get the whole benefit unless you can
> somehow manage to mark the pages PD_ALL_VISIBLE and set the visibility
> map bits. Without that, the next vacuum is going to dirty the whole
> heap anyway. Granted that's a bit better than having the next scan do
> it.
If the premise that we can do just-about-whatever with the relation (and
any sub-components, TOAST table, visibility map, etc) since it was
created in the same transaction and therefore isn't visible outside,
then I don't think that setting the visibility map bits would be a
problem..
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2011-03-24 21:54:21 | Re: Pre-set Hint bits/VACUUM FREEZE on data load..? |
| Previous Message | Stephen Frost | 2011-03-24 21:47:29 | Re: Pre-set Hint bits/VACUUM FREEZE on data load..? |