| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PSA: Autoconf has risen from the dead |
| Date: | 2022-01-24 14:14:27 |
| Message-ID: | 1871565.1643033667@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:
> I have patches ready for this at
> https://github.com/petere/postgresql/tree/autoconf-updates.
> My thinking was to wait until Autoconf 2.71 has trickled down into the
> OS versions that developers are likely to use.
I find that kind of irrelevant, because we expect people to install
autoconf from source anyway to avoid distro-specific behavior.
I suppose that waiting for it to get out into the wild might be good
from the standpoint of being sure it's bug-free, though.
Do these versions fix any bugs that affect us (i.e., that we've
not already created workarounds for)?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dipesh Pandit | 2022-01-24 14:29:55 | Re: refactoring basebackup.c |
| Previous Message | Peter Eisentraut | 2022-01-24 14:10:35 | Re: Skipping logical replication transactions on subscriber side |