Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem
| От | Claudio Freire |
|---|---|
| Тема | Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem |
| Дата | |
| Msg-id | CAGTBQpY3FUTLrXG-Tib4-r2TJvE_htGN3ufYLffmB6SXhOOVXQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem (Masahiko Sawada <sawada.mshk@gmail.com>) |
| Ответы |
Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem
|
| Список | pgsql-hackers |
On Wed, Feb 1, 2017 at 5:47 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> Thank you for updating the patch.
>
> Whole patch looks good to me except for the following one comment.
> This is the final comment from me.
>
> /*
> * lazy_tid_reaped() -- is a particular tid deletable?
> *
> * This has the right signature to be an IndexBulkDeleteCallback.
> *
> * Assumes dead_tuples array is in sorted order.
> */
> static bool
> lazy_tid_reaped(ItemPointer itemptr, void *state)
> {
> LVRelStats *vacrelstats = (LVRelStats *) state;
>
> You might want to update the comment of lazy_tid_reaped() as well.
I don't see the mismatch with reality there (if you consider
"dead_tples array" in the proper context, that is, the multiarray).
What in particular do you find out of sync there?
В списке pgsql-hackers по дате отправления: