| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Is this a typo? |
| Date: | 2025-11-11 03:32:27 |
| Message-ID: | 5EBF1771-0566-4D08-9F9B-CDCDEF4BDC98@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Hacker,
While working on the other patch and editing heapam.c, I noticed this in line 2251:
```
/*
* If tuple is cachable, mark it for invalidation from the caches in case
* we abort. Note it is OK to do this after releasing the buffer, because
* the heaptup data structure is all in local memory, not in the shared
* buffer.
*/
```
Is “cachable” a typo? I confirmed with a dictionary and it gave me “cacheable”. Maybe an acceptable old usage that I am not aware of? So, I want to confirm with the community.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-11-11 03:32:41 | Re: Logical Replication of sequences |
| Previous Message | Amit Kapila | 2025-11-11 03:18:58 | Re: Add support for COPY TO in tablesync for partitioned tables. |