| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Commitfest 2023-03 starting tomorrow! |
| Date: | 2023-03-19 20:56:14 |
| Message-ID: | 794454.1679259374@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> On 17.03.23 15:38, Tom Lane wrote:
>>> Simplify find_my_exec by using realpath(3)
>> The problem with this one is that Peter would like it to do something
>> other than what I think it should do. Not sure how to resolve that.
> I have no objection to changing the internal coding of the current behavior.
Oh ... where the thread trailed off [1] was you not answering whether
you'd accept a compromise behavior. If it's okay to stick with the
behavior we have, then I'll just do the original patch (modulo Munro's
observations about _fullpath's error reporting).
regards, tom lane
[1] https://www.postgresql.org/message-id/2319396.1664978360%40sss.pgh.pa.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-03-19 21:13:01 | Re: Infinite Interval |
| Previous Message | Joseph Koshakow | 2023-03-19 20:46:58 | Re: Infinite Interval |