| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Minor fix in pg_buffercache_evict documentation |
| Date: | 2025-01-31 09:53:04 |
| Message-ID: | 5B267A82-BBBE-4511-8A28-3A3462EA090F@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 31 Jan 2025, at 07:03, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> wrote:
>
> Hi All,
> All the functions in pg_buffercache module have their names suffixed
> with () and also use <function> tag in the documentation, except
> pg_buffercache_evict(). PFA patch to fix the style. With this change,
> the index entry and the section tile is displayed as "The
> pg_buffercache_evict() Function" instead of "The pg_buffercache_evict
> Function", which looks consistent with other function entries and
> section headers.
>
> This seems to be the only place where pg_buffercache_evict does not
> have suffix ().
I agree with this fix so I've applied it to master backpatched to v17 where
pg_buffercache_evict was introduced. Thanks!
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antonin Houska | 2025-01-31 10:15:24 | Re: why there is not VACUUM FULL CONCURRENTLY? |
| Previous Message | Laurenz Albe | 2025-01-31 09:32:54 | Re: Use "protocol options" name instead of "protocol extensions" everywhere |