| From: | Shadar <shauldar(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET? |
| Date: | 2009-06-11 14:32:51 |
| Message-ID: | 23982524.post@talk.nabble.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I notice that one of my tables gets TOASTed, about 40% of it. I read about
TOAST and understand the general motivation (get faster access to the
*other* columns). But in my case the big column (~2.5KB fixed width) is a
list (array) of values (not text) and the usage pattern is that I always
access a single row from the table by key and read the full list. So my
guess is TOAST is doing me more damage than good. Right?
I would have liked to disable TOAST (even altogether for my DB) - is there a
direct way to do this? Alternatively I thought of increasing
TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET from 2KB (I believe this is the
default?) to 4KB? Do I have to change the source (
http://doxygen.postgresql.org/tuptoaster_8h-source.html here ?) and compile
a private version of Postgres?
Thanks, feel free to reply by email.
-- Shaul (info(at)shauldar(dot)com)
--
View this message in context: http://www.nabble.com/Modifying-TOAST_TUPLE_THRESHOLD-and-TOAST_TUPLE_TARGET--tp23982524p23982524.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-06-11 14:50:13 | Re: pgindent run coming |
| Previous Message | Tom Lane | 2009-06-11 14:26:37 | Re: Problem with listen_addresses = '*' on 8.4beta2 on AIX |