From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | PostgreSQL HACKERS <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | type coerce problem with lztext |
Date: | 2000-02-27 12:03:37 |
Message-ID: | m12P2QD-0003kGC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Well,
LZTEXT is there again, and pg_rewrite uses it for action and
qual strings. This is what it tells:
pgsql=# select rulename, length(ev_action), octet_length(ev_action)
pgsql-# from pg_rewrite;
rulename | length | octet_length
----------------+--------+--------------
_RETpg_user | 3043 | 855
_RETpg_rules | 3074 | 1139
_RETpg_views | 4261 | 1252
_RETpg_tables | 5187 | 1338
_RETpg_indexes | 3525 | 1122
(5 rows)
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?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-02-27 14:48:16 | Re: [HACKERS] Changes in 7.0 |
Previous Message | Tatsuo Ishii | 2000-02-27 11:00:53 | Re: [HACKERS] Changes in 7.0 |