Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits
| От | Tom Lane |
|---|---|
| Тема | Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits |
| Дата | |
| Msg-id | 959.1554436678@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits |
| Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes:
> I think the right approach would be to do all of this in heap_insert and
> heap_multi_insert. Whenever starting to work on a page, if INSERT_FROZEN
> is specified, remember whether it is either currently empty, or is
> already marked as all-visible. If previously empty, mark it as all
> visible at the end. If already all visible, there's no need to change
> that. If not yet all-visible, no need to do anything, since it can't
> have been inserted with COPY FREEZE. Do you see any problem doing it
> that way?
Do we want to add overhead to these hot-spot routines for this purpose?
regards, tom lane
В списке pgsql-hackers по дате отправления: