Hi all,

I wrote a experimental patch for a vertical partitioning
function.

I decided to use the code of TOAST to create the function
easily. In a word, the row that the user specified is forcedly
driven out with TOAST.

The performance gain of 10% was seen by driving out c_data of the
customer table in the DBT-2 benchmark in our environment.

The mechanism of TOAST is an overdesigned system to use it for a
vertical partitioning. Because the overhead of processing is large,
the performance might down according to the environment.

There are seriously a lot of things that should be considered if
a vertical partitioning is mounted.
For instance, TOAST index is omitted, and ctid is used for link.

Your comments are welcome. Thanks.

---
How To Use
---
Use "ALTER TABLE" command.
http://www.postgresql.org/docs/8.1/static/sql-altertable.html

 ALTER TABLE name ALTER COLUMN column SET STRAGE FORCEEXTERNAL;

I do not understand whether "FORCEEXTERNAL" is an appropriate
word. Please teach when there is a better word...


-- 
Junji Teramoto

Responses

• Re: Vertical Partitioning with TOAST at 2005-12-08 05:02:27 from Jim C. Nasby

pgsql-hackers by date

Next:	From: Richard Huxton	Date: 2005-12-01 10:06:12
	Subject: Re: [HACKERS] Upcoming PG re-releases
Previous:	From: Tatsuo Ishii	Date: 2005-12-01 07:13:05
	Subject: Re: A couple of proposed pgbench changes