| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Laurent Laborde" <kerdezixe(at)gmail(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Higher TOAST compression. |
| Date: | 2009-07-22 15:25:42 |
| Message-ID: | 4A66E9260200002500028B99@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sorry I responded that quickly this early. I keep having additional
thoughts....
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> And especially, how could you have per-column targets?
> Yeah, this would have to be done by table, not by column.
If we had an optional two targets by column, we could pass any columns
with such targets as a "step 0", before starting the tuple size
checks. I think that makes sense, so I'm flip-flopping on that as a
possibility.
Now, whether that's overkill is another question.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2009-07-22 15:55:22 | Re: revised hstore patch |
| Previous Message | Kevin Grittner | 2009-07-22 15:08:11 | Re: Higher TOAST compression. |