Let me ask this differently: can Visual Studio 2013/2017 compile libpq with
openssl 1.1 support? Under Windows?
I have not been able to find an answer by googling before asking this
question here. Can someone share the compiled library and changes in the
source if needed for the openssl 1.1? Magnu
On Sun, Feb 25, 2018 at 09:06:39PM -0800, Adrian Klaver wrote:
> On 02/25/2018 08:36 PM, Konstantin Izmailov wrote:
>> I wonder if I'm not doing smth right, or libpq is not compatible with
>> openssl 1.1? Please help.
The answer to the second question is that libpq is compatible with
OpenSSL 1.1.0
On 02/25/2018 08:36 PM, Konstantin Izmailov wrote:
I got the latest libpq (from pg 10.1), and tried to compile it with
openssl 1.1. I got errors:
libpq10\fe-secure-openssl.c(1582): error C2037: left of 'ptr' specifies
undefined struct/union 'bio_st'
libpq10\fe-secure-openssl.c(1582): error C2198
I got the latest libpq (from pg 10.1), and tried to compile it with openssl
1.1. I got errors:
libpq10\fe-secure-openssl.c(1582): error C2037: left of 'ptr' specifies
undefined struct/union 'bio_st'
libpq10\fe-secure-openssl.c(1582): error C2198: 'pqsecure_raw_read' : too
few arguments for call
lib
On Sun, Feb 25, 2018 at 04:20:41PM -0500, Tom Lane wrote:
> No; you're reading the commits in reverse order. The hack I thought we
> could use to preserve that behavior didn't work.
>
> AFAICS, the only way we could maintain something like the old behavior
> here is to promote it to a full-fledg
Karsten Hilbert writes:
> On Mon, Jan 29, 2018 at 03:57:48AM +0100, David Fetter wrote:
>> Tom Lane pushed:
>> ... This leaves us with no solution for the
>> default_transaction_read_only issue that commit 4bd371f6f intended to work
>> around, other than "you gotta remove such settings before dump
On Mon, Jan 29, 2018 at 03:57:48AM +0100, David Fetter wrote:
> == PostgreSQL Weekly News - January 28 2018 ==
...
> == Applied Patches ==
...
> Tom Lane pushed:
...
> - In pg_dump, force reconnection after issuing ALTER DATABASE SET command(s).
> The folly of not doing this was exposed by the b
On 02/25/2018 10:11 AM, jotpe wrote:
This should eliminate this:
/usr/bin/install: Neu erstelltes
'/usr/share/postgresql/9.6/extension/bignum--0.8.0.sql' wird nicht mit
'.//sql/bignum--0.8.0.sql' überschrieben.
/usr/lib/postgresql/9.6/lib/pgxs/src/makefiles/pgxs.mk:114: die Regel
für Zie
Am 25.02.2018 um 16:42 schrieb Adrian Klaver:
On 02/25/2018 12:26 AM, jotpe wrote:
I could compile the pg-cert extension package, but postgresql 9.6
refused to install it.
create extension cert;
FEHLER: geschachteltes CREATE EXTENSION wird nicht unterstützt
means "ERROR: nested CREATE EXTEN
On 02/25/2018 12:26 AM, jotpe wrote:
I could compile the pg-cert extension package, but postgresql 9.6
refused to install it.
create extension cert;
FEHLER: geschachteltes CREATE EXTENSION wird nicht unterstützt
means "ERROR: nested CREATE EXTENSION is not supported"
At line 12 in /usr/share/
I could compile the pg-cert extension package, but postgresql 9.6
refused to install it.
create extension cert;
FEHLER: geschachteltes CREATE EXTENSION wird nicht unterstützt
means "ERROR: nested CREATE EXTENSION is not supported"
At line 12 in /usr/share/postgresql/9.6/extension/cert--0.1.1.s
11 matches
Mail list logo
