| From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Correct some doc items due to the REPACK |
| Date: | 2026-08-13 14:50:40 |
| Message-ID: | CAB-JLwZFLOzd7weRP5Qp+_Be3z2918od6cf7LXiFcEJwcY-WXg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Em qui., 13 de ago. de 2026 às 04:45, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
escreveu:
> - In mvcc.sgml, v1 added REPACK to the ACCESS EXCLUSIVE lock list in a
> way that made the CONCURRENTLY behavior ambiguous. I changed this to
> say that REPACK also acquires this lock mode, while REPACK CONCURRENTLY
> acquires it only when swapping the table and index files.
Cool, your version is much better than mine.
Only on mvcc.sgml I think mine is better because explains other commands
and both which have CONCURRENTLY option explained only once.
regards
Marcos
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2026-08-13 15:19:08 | Re: Logical replication row filter loses unchanged toasted columns |
| Previous Message | Greg Sabino Mullane | 2026-08-13 14:45:42 | Re: [PATCH] pg_upgrade: add --initdb option to create the new cluster automatically |