| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Remove TRACE_SORT macro? |
| Date: | 2024-08-07 06:56:30 |
| Message-ID: | be5f7162-7c1d-44e3-9a78-74dcaa6529f2@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I think we could remove the TRACE_SORT macro.
The TRACE_SORT macro has guarded the availability of the trace_sort GUC
setting. But it has been enabled by default ever since it was
introduced in PostgreSQL 8.1, and there have been no reports that
someone wanted to disable it. So I think we could just remove the macro
to simplify things.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Remove-TRACE_SORT-macro.patch | text/plain | 18.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2024-08-07 06:59:59 | RE: Conflict detection and logging in logical replication |
| Previous Message | Pavel Stehule | 2024-08-07 06:34:21 | Re: pgsql: Introduce hash_search_with_hash_value() function |