Goodnight,
Thank you very much for the answer.
I followed all the installation instructions: apply patch, compile
install postgres, etc.
I just tried everything with the UI ii) Manually (through psql session),
which is also mentioned in the readme, and everything works for me. But to
better test m
On 9/29/20 3:46 PM, Yessica Brinkmann wrote:
I will greatly appreciate a help with this topic please. I really need
to use that interface to be able to test my thesis. And I am not being
able to use.
Best regards,
Yessica Brinkmann
I didn't see any reported error messages in your post.
An
I will greatly appreciate a help with this topic please. I really need to use that interface to be able to test my thesis. And I am not being able to use.Best regards,Yessica Brinkmann Mensaje original Asunto: Gurjeet Singh Index Adviser User InterfaceDe: Yessica Brinkmann Para: pgs
Thanks, Tom. I really appreciate you taking the time to help me out!
I think I'm good now. I ran `readelf -d libpq.so | grep runpath` and I see
that the path I specified in --with-libraries is present (albeit after my
system path). It also appears the version I expected of libssl is being
used (li
Joshua Poehls writes:
> rpath and LD_LIBRARY_PATH are only relevant for the runtime
> linking/resolution, right? My concern is that at *compilation time* the
> wrong version of OpenSSL is being picked up.
No; --with-libraries will control what's linked against. The problem
you face is that the d
rpath and LD_LIBRARY_PATH are only relevant for the runtime
linking/resolution, right? My concern is that at *compilation time* the
wrong version of OpenSSL is being picked up. Is there a way to see the full
library/header path the compiler is using so that I can verify the path I
specified with --
Joshua Poehls writes:
> I'm compiling PG 12.2 (on CentOS 7) and need to ensure that it uses a
> specific version of OpenSSL (1.1.1h). I've added what I think are the
> appropriate `./configure` flags (see below) and compilation is successful
> but when I run `ldd -d initdb` or `readelf` I can see
I'm compiling PG 12.2 (on CentOS 7) and need to ensure that it uses a
specific version of OpenSSL (1.1.1h). I've added what I think are the
appropriate `./configure` flags (see below) and compilation is successful
but when I run `ldd -d initdb` or `readelf` I can see that it linked to a
different v
> On 29 Sep 2020, at 17:16, Jehan-Guillaume de Rorthais wrote:
>
> Sorry, there was some misunderstanding of the source code on my side. The
> "keepalives" parameter is enabled by default on client side, but if you don't
> set keepalives_idle, keepalives_interval and keepalives_count, they fal
On Tue, 29 Sep 2020 16:22:18 +0300
Олег Самойлов wrote:
[...]
> > In regards with keepalive parameters, I am a bit surprised. According to the
> > source code, parameters defaults are:
> >
> > keepalives=1
> > keepalives_idle=1
> > keepalives_interval=1
> > keepalives_count=1
> >
> > But I j
> On 29 Sep 2020, at 12:31, Jehan-Guillaume de Rorthais wrote:
>
> On Thu, 24 Sep 2020 15:22:46 +0300
> Олег Самойлов wrote:
>
>> Hi, Jehan.
>>
>>> On 9 Sep 2020, at 18:19, Jehan-Guillaume de Rorthais
>>> wrote:
>>>
>>> On Mon, 7 Sep 2020 23:46:17 +0300
>>> Олег Самойлов wrote:
>>>
On Thu, 24 Sep 2020 15:22:46 +0300
Олег Самойлов wrote:
> Hi, Jehan.
>
> > On 9 Sep 2020, at 18:19, Jehan-Guillaume de Rorthais
> > wrote:
> >
> > On Mon, 7 Sep 2020 23:46:17 +0300
> > Олег Самойлов wrote:
> >
> >>> [...]
> >> 10:30:55.965 FATAL: terminating walreceiver process dpue
12 matches
Mail list logo
