From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Andrus <kobruleht2(at)hot(dot)ee>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Using compression on TCP transfer |
Date: | 2020-03-31 12:33:55 |
Message-ID: | 1e7536de1cb9e1097d1c8faf07a08bf66d8eeead.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 2020-03-31 at 15:13 +0300, Andrus wrote:
> > It is a simple ALTER TABLE.
>
> Client is Visual FoxPro application. It sends data with trailing spaces
> sometimes and sometimes not.
> In case of varchar field values will appear in database sometimes with
> trailing spaces and sometimes without.
> This requires major application re-design which much is more expensive than
> continuing using char fields.
A simple BEFORE INSERT OR UPDATE trigger would take care of that.
> > You'd have to use an OpenSSL library with compression support enabled.
>
> Should I change OpenSSL installed from standard repository in Debian server
> or can it changed only for PostgreSql.
> How ?
I don't know if Debian's binaries are built with compression support,
probably not. You can build OpenSSL yourself and make PostgreSQL
use these binaries.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Pepe TD Vo | 2020-03-31 14:15:19 | migrate off oracle data to postgres |
Previous Message | Turritopsis Dohrnii Teo En Ming | 2020-03-31 12:28:01 | Re: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB? |