| From: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
|---|---|
| To: | Antonin Houska <ah(at)cybertec(dot)at> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Treat <rob(at)xzilla(dot)net> |
| Subject: | Re: Adding REPACK [concurrently] |
| Date: | 2026-01-12 18:20:35 |
| Message-ID: | CADzfLwUJSHKGxYw+vMUZ_Hr2YeuxO2Q5w13HKgUUN1725tjY5Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello, Antonin!
More comments - now for 0005 (but v29, but I think they are mostly up to date).
--- 0005 ---
> potentiallly
extra 'l' in commit message
> Memory the queue is located int.
"in"?
> again if its still eligible
if it's still eligible
> int initialized;
probably better to be bool (as in shared)
> DecodingWorkerState
such type does not exists in commit
> REPACK_WORKER_MAIN
Not used in code anywhere.
> int64 timeout = 0;
> WaitLSNResult res;
formatting issue here (tab vs space)
> if (size >= MaxAllocSize)
Seems like we lost that check, I think it may be executed on storing
the data or before "tup = (HeapTuple) palloc(HEAPTUPLESIZE + t_len);"
in apply_concurrent_changes
> bool done;
I still think it is a confusing name.
> chgdst.file_seq = WORKER_FILE_SNAPSHOT + 1;
I think it is better to increment it once a snapshot is received. And
rename to last_processed/last_improrted to be aligned with
last_exported.
Best regards,
Mikhail.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2026-01-12 18:22:20 | Use CASEFOLD() internally rather than LOWER() |
| Previous Message | Matheus Alcantara | 2026-01-12 18:07:21 | Re: PL/Python initialization cleanup |