| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fixing typos and inconsistencies |
| Date: | 2019-08-20 10:15:45 |
| Message-ID: | 20190820101545.GA1684@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 19, 2019 at 10:19:19PM +0300, Alexander Lakhin wrote:
> Now that the unicums checking is finished, I would like to share the
> script I used to find them.
> Maybe it can be useful to recheck the source tree from time to time...
> I don't think that the check could be fully automated, but with some
> eyeballing it allows to maintain a more consistent state.
Cool, thanks for sharing.
We still have a couple of things left though, one which stood out
recently was a reference to TupleLockUpdate in heapam.c. This relates
to multixact, so I am not actually sure to which lock level this was
referring to.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2019-08-20 10:34:13 | Re: Make SQL/JSON error code names match SQL standard |
| Previous Message | Thomas Munro | 2019-08-20 09:02:18 | Re: POC: Cleaning up orphaned files using undo logs |