From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-12-06
Date: Mon, 7 Dec 2020 19:42:19 +0100 [thread overview]
Message-ID: <20201207194219.507e55af@gmx.net> (raw)
In-Reply-To: <20201207101650.4aaf5988@windsurf.home>
Hello Maxim, Thomas,
On Mon, 7 Dec 2020 10:16:50 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Mon, 7 Dec 2020 11:56:24 +0300
> Maxim Kochetkov <fido_max@inbox.ru> wrote:
>
> > TimescaleDB have no PostgreSQL 13 support right now.
> >
> > https://github.com/timescale/timescaledb/blob/master/CMakeLists.txt
> >
> > # Ensure that PostgreSQL version is supported and consistent
> > # with src/compat.h version check
> > if ((${PG_VERSION_MAJOR} LESS "11") OR
> > (${PG_VERSION_MAJOR} GREATER "12"))
> > message(FATAL_ERROR "TimescaleDB only supports PostgreSQL 11 and 12")
> > endif()
>
> Then, how do we proceed, since timescaledb requires PostgreSQL, but
> Buildroot now uses PostgreSQL 13 ? Should we drop timescaledb ? Under
> what time frame does the timescaledb project intends to support
> PostgreSQL 13 ? There is apparently a pull request opened at
> https://github.com/timescale/timescaledb/pull/2498.
No urgent demand for the postgresql update from my side (as the 12.x
version is still supported with updates) in case timescaledb will
not provide an update in the near future (and the pull request is to
voluminous for an backport)...
Regards,
Peter
>
> Thomas
prev parent reply other threads:[~2020-12-07 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1kmBem-00064q-IV.thomas-petazzoni-bootlin-com@mx261.i.mail.ru>
[not found] ` <23e2d4ac-27ba-3967-36da-d1ae1ddfa050@inbox.ru>
2020-12-07 9:16 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-12-06 Thomas Petazzoni
2020-12-07 18:42 ` Peter Seiderer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201207194219.507e55af@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox