| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Have postgres.bki self-identify |
| Date: | 2025-03-20 20:10:32 |
| Message-ID: | CA+Tgmobj3FMoMUE13t6NMJHrSJiCTjrqhVDK+=MAhU8PuZNfAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 20, 2025 at 3:47 PM David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> While trying to find postgres.bki in my build directory searching for the file name didn't work because there is no comment in the file containing the file name; like there is in every other file we write or generate, including the related *_d.h files. Add it.
I'm not a fan of making it a policy that everyone has to do this. I'd
rather see us remove filenames from some places where they cause
maintenance overhead for little benefit. If somebody wants to find
postgres.bki, I guess you can just "find . -name postgres.bki -print"
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2025-03-20 20:16:44 | Re: md.c vs elog.c vs smgrreleaseall() in barrier |
| Previous Message | Robert Haas | 2025-03-20 20:06:59 | Re: Proposal: Progressive explain |