Re: Using compression on TCP transfer
| От | Laurenz Albe | 
|---|---|
| Тема | Re: Using compression on TCP transfer | 
| Дата | |
| Msg-id | 1e7536de1cb9e1097d1c8faf07a08bf66d8eeead.camel@cybertec.at обсуждение исходный текст  | 
		
| Ответ на | Re: Using compression on TCP transfer ("Andrus" <kobruleht2@hot.ee>) | 
| Ответы | 
                	
            		Re: Using compression on TCP transfer
            		
            		 | 
		
| Список | 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
В списке pgsql-general по дате отправления: