On Tue, 16 Jun 2015 04:45:52 -0300
"Leonardo M. Ramé" wrote:
> Hi, does anyone know if there's a compression function to let me store
> in gzipped/deflate format TEXT or Bytea fields.
>
> Please correct me if I'm wrong, but I also wonder if this function is
> really needed since I've read larg
Leonardo M. Ramé wrote:
> Hi, does anyone know if there's a compression function to let me store
> in gzipped/deflate format TEXT or Bytea fields.
>
> Please correct me if I'm wrong, but I also wonder if this function is
> really needed since I've read large objects are stored with TOAST, hence
>
Where do I find more information about PG fork you mentioned?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Compression-tp4304322p5727363.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-gener
On Mon, 5 Sep 2011 14:23:12 +0300, Oguz Yilmaz wrote:
Hi,
We need some handy method for compression of pgsql communication on
port 5432. For my case, database is available over the internet and
application logic has to reach the database remotely.
I have searched for it and found those threads:
On Thursday, April 14, 2011 9:37:10 pm Craig Ringer wrote:
> On 15/04/2011 8:07 AM, Adrian Klaver wrote:
> > "EXTENDED allows both compression and out-of-line storage. This is the
> > default for most TOAST-able data types. Compression will be attempted
> > first, then out-of-
> >
> > line storage
On 15/04/2011 8:07 AM, Adrian Klaver wrote:
"EXTENDED allows both compression and out-of-line storage. This is the
default for most TOAST-able data types. Compression will be attempted
first, then out-of-
line storage if the row is still too big. "
Good point. I was unclear; thanks for pointi
>> Cc: pgsql-general@postgresql.org; Craig Ringer
>> Subject: Re: [GENERAL] Compression
>>
>> On Thu, Apr 14, 2011 at 5:07 PM, Adrian Klaver
>> wrote:
>> > On Thursday, April 14, 2011 4:50:44 pm Craig Ringer wrote:
>> >
>> >> On 15/04/2
On Thursday, April 14, 2011 7:46:34 pm Yang Zhang wrote:
> On Thu, Apr 14, 2011 at 7:42 PM, Adrian Klaver
wrote:
> > Granted no all data types are TOASTable. Are you looking for something
> > more aggressive than that?
>
> Yes.
>
> http://blog.oskarsson.nu/2009/03/hadoop-feat-lzo-save-disk-spa
On Thu, Apr 14, 2011 at 7:42 PM, Adrian Klaver wrote:
> On Thursday, April 14, 2011 5:51:21 pm Yang Zhang wrote:
>
>> >
>
>> > adrian.kla...@gmail.com
>
>>
>
>> Already know about TOAST. I could've been clearer, but that's not the
>
>> same as the block-/page-level compression I was referring to.
On Thursday, April 14, 2011 5:51:21 pm Yang Zhang wrote:
> >
> > adrian.kla...@gmail.com
>
> Already know about TOAST. I could've been clearer, but that's not the
> same as the block-/page-level compression I was referring to.
I am obviously missing something. The TOAST mechanism is designed t
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Yang Zhang
> Sent: Thursday, April 14, 2011 6:51 PM
> To: Adrian Klaver
> Cc: pgsql-general@postgresql.org; Craig Ringer
> Subject: Re:
On Thu, Apr 14, 2011 at 5:07 PM, Adrian Klaver wrote:
> On Thursday, April 14, 2011 4:50:44 pm Craig Ringer wrote:
>
>> On 15/04/2011 7:01 AM, Yang Zhang wrote:
>
>> > Is there any effort to add compression into PG, a la MySQL's
>
>> > row_format=compressed or HBase's LZO block compression?
>
>>
>
On Thursday, April 14, 2011 4:50:44 pm Craig Ringer wrote:
> On 15/04/2011 7:01 AM, Yang Zhang wrote:
> > Is there any effort to add compression into PG, a la MySQL's
> > row_format=compressed or HBase's LZO block compression?
>
> There's no row compression, but as mentioned by others there is
> o
On 15/04/2011 7:01 AM, Yang Zhang wrote:
Is there any effort to add compression into PG, a la MySQL's
row_format=compressed or HBase's LZO block compression?
There's no row compression, but as mentioned by others there is
out-of-line compression of large values using TOAST.
Row compression w
On Thursday, April 14, 2011 4:01:54 pm Yang Zhang wrote:
> Is there any effort to add compression into PG, a la MySQL's
> row_format=compressed or HBase's LZO block compression?
TOAST?
http://www.postgresql.org/docs/9.0/interactive/storage-toast.html
--
Adrian Klaver
adrian.kla...@gmail.com
--
On 02/24/11 10:55 PM, Yang Zhang wrote:
For various workloads, compression could be a win on both disk space
and speed (see, e.g.,
http://blog.oskarsson.nu/2009/03/hadoop-feat-lzo-save-disk-space-and.html).
I realize Postgresql doesn't have general table compression a la
InnoDB's row_format=com
On Fri, Aug 13, 2010 at 10:56 AM, Joshua D. Drake
wrote:
> On Fri, 2010-08-13 at 11:38 -0400, Tom Lane wrote:
>>
>> I don't really see that. The case where it's sensible to use
>> compression on the connection is where you're pushing data across
>> a WAN. That's also pretty much exactly the sit
Bruce Momjian wrote:
> Craig Ringer wrote:
>
>> On 13/08/2010 9:31 PM, Bruce Momjian wrote:
>>
>>> Karl Denninger wrote:
>>>
I may be blind - I don't see a way to enable this. OpenSSL "kinda"
supports this - does Postgres' SSL connectivity allow it to be
supported/ena
On Fri, 2010-08-13 at 11:38 -0400, Tom Lane wrote:
> Craig Ringer writes:
> > Overall: it sounds to me like SSL/TLS level compression would only be
> > useful for native libpq-to-postgresql connections, and probably wouldn't
> > be usable for non-libpq based database access drivers. It'd only wo
Craig Ringer writes:
> Overall: it sounds to me like SSL/TLS level compression would only be
> useful for native libpq-to-postgresql connections, and probably wouldn't
> be usable for non-libpq based database access drivers. It'd only work if
> SSL was configured, which is a limitation it'd be
On 13/08/2010 10:50 PM, Bruce Momjian wrote:
I thought all SSL traffic was compressed, unless you turned that off.
It is just SSH that is always compressed?
Frankly, I thought all SSL traffic was compressed too, but the reading
I've just been doing suggests otherwise. It looks like compressio
On 13/08/2010 10:43 PM, Craig Ringer wrote:
OpenSSL does provide some transparent crypto support. See:
http://www.openssl.org/docs/ssl/SSL_COMP_add_compression_method.html
Some more info on this:
Apache mod_ssl docs mention that SSLv3 handshake is required to
negotiate compression in SSL. Th
Craig Ringer wrote:
> On 13/08/2010 9:31 PM, Bruce Momjian wrote:
> > Karl Denninger wrote:
> >> I may be blind - I don't see a way to enable this. OpenSSL "kinda"
> >> supports this - does Postgres' SSL connectivity allow it to be
> >> supported/enabled?
> >
> > What are you asking, exactly?
>
>
On 13/08/2010 9:31 PM, Bruce Momjian wrote:
Karl Denninger wrote:
I may be blind - I don't see a way to enable this. OpenSSL "kinda"
supports this - does Postgres' SSL connectivity allow it to be
supported/enabled?
What are you asking, exactly?
As far as I can tell they're asking for transp
Karl Denninger wrote:
> I may be blind - I don't see a way to enable this. OpenSSL "kinda"
> supports this - does Postgres' SSL connectivity allow it to be
> supported/enabled?
What are you asking, exactly?
--
Bruce Momjian http://momjian.us
EnterpriseDB
25 matches
Mail list logo
