Hi all!
It's possible that pldebugger12 does not exists for centos 7?
Thanks a lot,
Diego
On 2020-09-07 10:16, Lucas Luengas wrote:
Centos 6:
https://download.postgresql.org/pub/repos/yum/12/redhat/rhel-6-x86_64/pldebugger12-1.1-1.rhel6.1.x86_64.rpm
https://download.postgresql.org/pub/repos/y
> On 3 Sep 2020, at 17:25, Jehan-Guillaume de Rorthais wrote:
>
> On Wed, 2 Sep 2020 20:33:09 +0300
> Олег Самойлов wrote:
>
>> The software is rather outdated. It works with PostgreSQL 11 and CentOS 7.
>> The next step will be upgrading to CentOS 8 and PostgreSQL 12. Please tell
>> me, is i
Hi
> On 3 Sep 2020, at 14:39, Jehan-Guillaume de Rorthais wrote:
> On Mon, 24 Aug 2020 18:45:42 +0300
> Олег Самойлов wrote:
>
>>> 21 авг. 2020 г., в 17:26, Jehan-Guillaume de Rorthais
>>> написал(а):
>>>
>>> On Thu, 20 Aug 2020 15:16:10 +0300
>>> Based on setup per node, you can probably add
On 9/7/20 9:06 AM, Laurenz Albe wrote:
[snip]
However, if I were you, I'd refuse to support any PostgreSQL major
version that is no longer supported by the project:
https://www.postgresql.org/support/versioning/
So, nothing older than 9.5.
That's grossly unrealistic.
--
Angular momentum makes
On Mon, 2020-09-07 at 11:22 +0200, Matthias Apitz wrote:
> Is there some matrix about which PG client versions, esp. the shared
> libs of ESQL/C can work with which PG server versions. We have a case
> where a customer wants to use his own PG server, perhaps even on
> Windows, with our 11.4 client
Hello,
Is there some matrix about which PG client versions, esp. the shared
libs of ESQL/C can work with which PG server versions. We have a case
where a customer wants to use his own PG server, perhaps even on
Windows, with our 11.4 client version (compiled by us) and used via
ESQL/C.
Thanks
> t > '2020-01-01'::timestamp and t < '2021-01-01'::timestamp
>Not at all important, but it seems odd to be exclusive of the start and end
>both. I would >consider including the start with >=
>Michael Lewis | Database Engineer
>Entrata
Michael, funny I was thinking that myself minutes after posti
‐‐‐ Original Message ‐‐‐
On Monday, September 7, 2020 9:04 AM, Klaudie Willis
wrote:
> Maybe the right way to improve this is to bypass add_paths_to_append_rel
> entirely when there's exactly one surviving child rel, and make it
> just use all the surviving paths for that child.
> re
