Re: [HACKERS] LZTEXT for rule plan stings - Mailing list pgsql-hackers

From Don Baccus
Subject Re: [HACKERS] LZTEXT for rule plan stings
Date
Msg-id 3.0.1.32.20000226105512.016e6c60@mail.pacifier.com
Whole thread Raw
In response to Re: [HACKERS] LZTEXT for rule plan stings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 12:15 PM 2/26/00 -0500, Tom Lane wrote:

>and (except for not using any excess whitespace) that is exactly what
>goes into a rule action string.
>
>As you can see, this is very amenable to compression, especially
>when you have a lot of columns in a view.
>
>Someday we might think about using a more compact representation for
>stored rules, but there are advantages to using a format that's fairly
>easy for a human to examine.

Oh, now I understand, I didn't realize the tree was being stored in
human-readable form as a string, but thought it was being parsed into
a binary form.  That's why I began having doubts that I might've triggered
unecessary work on Jan's part regarding lztext.  Yes, since it's
stored as a text string lztext should help a LOT.



- Don Baccus, Portland OR <dhogaza@pacifier.com> Nature photos, on-line guides, Pacific Northwest Rare Bird Alert
Serviceand other goodies at http://donb.photo.net.
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] LZTEXT for rule plan stings
Next
From: Don Baccus
Date:
Subject: Re: [HACKERS] LZTEXT for rule plan stings