| From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Fix smgrtruncate code comment. |
| Date: | 2024-07-29 10:50:27 |
| Message-ID: | CALdSSPh9VA6SDSVjrcmSPEYramf+rFisK7GqJo1dtRnD3vddmA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Today I was busy rebasing my Greenplum-related Extendable SMGR
patches on Cloudberry, and I faced some conflicts.
While resolving them I noticed code & comments inconsistency in smgr.c
in smgrtruncate function, which tracks down to
c5315f4f44843c20ada876fdb0d0828795dfbdf5. In this commit,
smgr_fsm_nblocks & smgr_vm_nblocks fields were removed, however
comments were not fixed accordingly.
So i suggest to fix this, PFA
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Fix-smgrtruncate-code-comment.patch | application/octet-stream | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2024-07-29 10:54:15 | Re: why is pg_upgrade's regression run so slow? |
| Previous Message | vignesh C | 2024-07-29 10:48:33 | Re: Logical Replication of sequences |