On Tue, Jul 5, 2016 at 7:46 AM, Krzysztof Kaczkowski
wrote:
> Thanks to emails, we have achieved what we wanted. This is what we’ve done:
>
> Compilation (for 32 bit version, initdb with locale=C):
>
> CFLAGS="-mx32 -fexcess-precision=standard -O2"
> CXXFLAGS="-mx32"
>
> configure --without-zlib -
Hello,
Thanks to emails, we have achieved what we wanted. This is what we’ve done:
Compilation (for 32 bit version, initdb with locale=C):
CFLAGS="-mx32 -fexcess-precision=standard -O2"
CXXFLAGS="-mx32"
configure --without-zlib --disable-float8-byval --without-readline
--host=x86_64-linux-gnux3
As someone who has bitten by index corruption due to collation changes
between glibc versions that shipped CentOS 6 and CentOS 7, don't even try
to do this with anything other than C collation. The default collation
_will_ deterministically leave you with a silently corrupt database if you
store an
Craig Ringer writes:
> On 4 July 2016 at 17:33, Krzysztof Kaczkowski wrote:
>> We know that standard PostgreSQL is not able to use cluster created on
>> different OS. We think that recompilation PostgreSQL with some specific
>> flags. This should give us compatibility of cluster on different Syst
Hello,
About Your question, please do not ask. This infrastructure is an outcome
of a very long talk with supervisors.
Back to the topic. I like the tricky part. Do You think there is some way
to achieve this on compilation level or shall we search somewhere else? For
example UNIX libraries or ev
On 4 July 2016 at 17:33, Krzysztof Kaczkowski wrote:
> Hello everyone,
>
> Right now we have PostgreSQL on Windows Server (main data center) and
> cluster is placed on NAS. We have emergency data center on UNIX
> architecture. We want that emergency data center could continue work on
> PostgreSQL
