Re: [HACKERS] type coerce problem with lztext - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] type coerce problem with lztext
Date
Msg-id 200002271450.JAA28342@candle.pha.pa.us
Whole thread Raw
In response to type coerce problem with lztext  (wieck@debis.com (Jan Wieck))
Responses Re: [HACKERS] type coerce problem with lztext  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
>     Yes, the 3043 bytes long rule action string got stored in 855
>     bytes  in  pg_rewrite.  That's 71.9% compression rate on this
>     attempt!
> 
>     There are functions text(lztext) and  lztext(text)  too,  but
>     the  system  is  unable  to  find an operator if one compares
>     text=lztext in a query. IIRC, creating a  function  named  as
>     the target type and taking the source type is what made auto-
>     type-conversion work - so what am I missing here?

Added to Features:
New lztext data type for compressed text fieldsLarger views/rules supported

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: type coerce problem with lztext
Next
From: Don Baccus
Date:
Subject: Re: [HACKERS] type coerce problem with lztext