| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remove latch.c workaround for Linux < 2.6.27 |
| Date: | 2021-02-27 03:45:07 |
| Message-ID: | 390458.1614397507@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Commit 82ebbeb0 added a workaround for (already in 2017) ancient Linux
> kernels with no EPOLL_CLOEXEC. I don't see any such systems in the
> build farm today (and if there is one hiding in there somewhere, it's
> well past time to upgrade). I'd like to rip that code out, because
> I'm about to commit some new code that uses another 2.6.17+
> XXX_CLOEXEC flag, and it'd be silly to have to write new workaround
> code for that too, and a contradiction to have fallback code in one
> place but not another. Any objections?
I believe we've dropped support for RHEL5, so no objection here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-02-27 04:02:19 | Re: repeated decoding of prepared transactions |
| Previous Message | Amit Kapila | 2021-02-27 03:17:54 | Re: [HACKERS] logical decoding of two-phase transactions |