On Fri, Feb 4, 2022 at 8:12 AM Andres Freund wrote:
> On 2022-02-03 10:44:11 +0100, Fabien COELHO wrote:
> > For these reasons, I'm inclined to let seawasp as it is.
It might be easier to use the nightly packages at
https://apt.llvm.org/. You could update daily and still save so much
CPU that ..
Hi,
On 2022-02-03 10:44:11 +0100, Fabien COELHO wrote:
> > I'm doubtful that tracking development branches of LLVM is a good
> > investment. Their development model is to do changes in-tree much more than
> > we
> > do. Adjusting to API changes the moment they're made will often end up with
> > f
Hello Andres,
I'm doubtful that tracking development branches of LLVM is a good
investment. Their development model is to do changes in-tree much more than we
do. Adjusting to API changes the moment they're made will often end up with
further changes to the same / related lines. Once they open
Hi,
On 2022-01-30 21:38:16 -0500, Tom Lane wrote:
> Speaking of buildfarm breakage, seawasp has been failing for the
> past several days. It looks like bleeding-edge LLVM has again
> changed some APIs we depend on. First failure is here:
I'm doubtful that tracking development branches of LLVM i
Speaking of buildfarm breakage, seawasp has been failing for the
past several days. It looks like bleeding-edge LLVM has again
changed some APIs we depend on. First failure is here:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=seawasp&dt=2022-01-28%2000%3A17%3A48
Indeed.
I'm so
On Mon, Jan 31, 2022 at 3:38 PM Tom Lane wrote:
> Speaking of buildfarm breakage, seawasp has been failing for the
> past several days. It looks like bleeding-edge LLVM has again
> changed some APIs we depend on. First failure is here:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=
Speaking of buildfarm breakage, seawasp has been failing for the
past several days. It looks like bleeding-edge LLVM has again
changed some APIs we depend on. First failure is here:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=seawasp&dt=2022-01-28%2000%3A17%3A48
