Building postgresql from sources, statically linked, linux

2nd docker build output === Anybody has an idea why this does not work or what I am doing wrong and how I can get a statically linked binary? Without the LDFLAGS the build and the initdb work fine. Thanks in advance, Rob

Re: jsonb_set() strictness considered harmful to data

> On Jan 17, 2020, at 4:28 PM, Ariadne Conill wrote: > > Hello, > > January 17, 2020 5:21 PM, "Tomas Vondra" > wrote: > > Thank you very much for coming together and finding a solution to this bug! > > Ariadne Let’s leave it at “issue” :)

Fix for Bug #16032

72ecfec Mon Sep 17 00:00:00 2001 From: Rob Emery Date: Tue, 1 Oct 2019 23:51:52 +0100 Subject: [PATCH] Fix bug16032; under windows when the backup is aborted or fails, pg_basebackup is unable to cleanup the backup as the filehandles haven't been released --- src/bin/pg_basebackup/

Re: CHAR vs NVARCHAR vs TEXT performance

nd TEXT (possibly a question for the JDBC guys rather than here)? Thanks, Rob On 2019-04-30 00:16, Thomas Munro wrote: On Tue, Apr 30, 2019 at 5:44 AM Tom Lane wrote: FWIW, my recommendation for this sort of thing is almost always to not use CHAR(n). The use-case for that datatype pretty much

CHAR vs NVARCHAR vs TEXT performance

use npgsql only sends TEXT whereas other drivers tend to send VARCHAR (other drivers includes the official JDBC driver). I guess the root question is: is TEXT supposed to be identical to VARCHAR in all scenarios? Thanks, Rob