| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cleaning up historical portability baggage |
| Date: | 2022-07-10 15:25:40 |
| Message-ID: | CAM-w4HPSo8y2us-jhv06AEhzFXyWYEWOMnRqYg7ZU6z9KwrAiw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 9 Jul 2022 at 21:46, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
>
> Hello,
>
> I wonder how much dead code for ancient operating systems we could now
> drop.
> 0002-Remove-dead-getrusage-replacement-code.patch
I thought the getrusage replacement code was for Windows. Does
getrusage on Windows actually do anything useful?
More generally I think there is a question about whether some of these
things are "supported" in only a minimal way to satisfy standards but
maybe not in a way that we actually want to use. Getrusage might exist
on Windows but not actually report the metrics we need, reentrant
library functions may be implemented by simply locking instead of
actually avoiding static storage, etc.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2022-07-10 15:26:18 | Re: Two successive tabs in test case are causing syntax error in psql |
| Previous Message | Tom Lane | 2022-07-10 14:36:08 | Re: Cleaning up historical portability baggage |