File: sql-cluster.html

package info (click to toggle)
mpsql 2.1-2
links: PTS
area: non-free
in suites: potato
size: 3,528 kB
ctags: 4,886
sloc: ansic: 35,184; makefile: 3,761; sh: 44
file content (410 lines) | stat: -rw-r--r-- 6,245 bytes
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>  CLUSTER
 </TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet version 1.19"><LINK
REL="HOME"
TITLE="PostgreSQL User's Guide"
HREF="user.html"><LINK
REL="UP"
TITLE="SQL Commands"
HREF="sql-commands.html"><LINK
REL="PREVIOUS"
TITLE="   CLOSE
  "
HREF="sql-close.html"><LINK
REL="NEXT"
TITLE="   COMMIT
  "
HREF="sql-commit.html"></HEAD
><BODY
BGCOLOR="#FFFFFF"
TEXT="#000000"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PostgreSQL User's Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="sql-close.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="sql-commit.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
>CLUSTER</H1
><DIV
CLASS="REFNAMEDIV"
><H2
>Name</H2
>  CLUSTER
  &#8212;   Gives storage clustering advice to the backend
 </DIV
><DIV
CLASS="REFSYNOPSISDIV"
><PRE
CLASS="SYNOPSIS"
>CLUSTER <TT
CLASS="REPLACEABLE"
><I
>indexname</I
></TT
> ON <TT
CLASS="REPLACEABLE"
><I
>table</I
></TT
>
 </PRE
><DIV
CLASS="REFSECT2"
><H3
>  Inputs
  </H3
><P
>  </P
><P
></P
><DL
><DT
><TT
CLASS="REPLACEABLE"
><I
>indexname</I
></TT
></DT
><DD
><P
>    The name of an index.
   </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>table</I
></TT
></DT
><DD
><P
>    The name of a table.
   </P
></DD
></DL
></DIV
><DIV
CLASS="REFSECT2"
><H3
>  Outputs
  </H3
><P
>    <P
></P
></P><DL
><DT
><SPAN
CLASS="RETURNVALUE"
>CLUSTER</SPAN
></DT
><DD
><P
>	  The clustering was done successfully.
	 </P
></DD
><DT
><SPAN
CLASS="RETURNVALUE"
>ERROR: relation &lt;<TT
CLASS="REPLACEABLE"
><I
>tablerelation_number</I
></TT
>&gt; inherits "invoice"</SPAN
></DT
><DD
><P
>&#13;	  
	 </P
></DD
><DT
><SPAN
CLASS="RETURNVALUE"
>ERROR: Relation x does not exist!</SPAN
></DT
><DD
><P
>&#13;	  
	 </P
></DD
></DL
><P>
  
 </P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><H2
>  Description
 </H2
><P
>  <B
CLASS="COMMAND"
>CLUSTER</B
> instructs <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> 
to cluster the class specified
  by <TT
CLASS="REPLACEABLE"
><I
>classname</I
></TT
> approximately
  based on the index specified by
  <TT
CLASS="REPLACEABLE"
><I
>indexname</I
></TT
>. The index must
  already have been defined on 
<TT
CLASS="REPLACEABLE"
><I
>classname</I
></TT
>.
 </P
><P
>  When a class is clustered, it is physically reordered
  based on the index information. The clustering is static.
  In other words, as the class is updated, the changes are
  not clustered. No attempt is made to keep new instances or
  updated tuples clustered.  If one wishes, one can
  recluster manually by issuing the command again.
 </P
><DIV
CLASS="REFSECT2"
><H3
>  Notes
  </H3
><P
> </P
><P
>  The table is actually copied to a temporary table in index
  order, then renamed back to the original name.  For this
  reason, all grant permissions and other indexes are lost
  when clustering is performed.
 </P
><P
>  In cases where you are accessing single rows randomly
  within a table, the actual order of the data in the heap
  table is unimportant. However, if you tend to access some
  data more than others, and there is an index that groups
  them together, you will benefit from using <B
CLASS="COMMAND"
>CLUSTER</B
>.
 </P
><P
> 
  Another place <B
CLASS="COMMAND"
>CLUSTER</B
> is helpful is in cases where you use an
  index to pull out several rows from a table. If you are
  requesting a range of indexed values from a table, or a
  single indexed value that has multiple rows that match,
  <B
CLASS="COMMAND"
>CLUSTER</B
> will help because once the index identifies the
  heap page for the first row that matches, all other rows
  that match are probably already on the same heap page,
  saving disk accesses and speeding up the query.
 </P
><P
>  There are two ways to cluster data. The first is with the
  <B
CLASS="COMMAND"
>CLUSTER</B
> command, which reorders the original table with
  the ordering of the index you specify. This can be slow
  on large tables because the rows are fetched from the heap
  in index order, and if the heap table is unordered, the
  entries are on random pages, so there is one disk page
  retrieved for every row moved. <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> has a cache,
  but the majority of a big table will not fit in the cache.
 </P
><P
> 
  Another way to cluster data is to use
<PRE
CLASS="PROGRAMLISTING"
>SELECT ... INTO TABLE <TT
CLASS="REPLACEABLE"
><I
>temp</I
></TT
> FROM ... ORDER BY ...</PRE
>
  This uses the <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> sorting code in
  ORDER BY to match the index, and is much faster for
  unordered data. You then drop the old table, use
<B
CLASS="COMMAND"
>ALTER TABLE/RENAME</B
>
 to rename <TT
CLASS="REPLACEABLE"
><I
>temp</I
></TT
> to the old name, and
  recreate any indexes. The only problem is that <SPAN
CLASS="ACRONYM"
>OID</SPAN
>s
  will not be preserved. From then on, <B
CLASS="COMMAND"
>CLUSTER</B
> should be
  fast because most of the heap data has already been
  ordered, and the existing index is used.
 </P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><H2
>  Usage
 </H2
><P
>  Cluster the employees relation on the basis of its salary attribute
 </P
><PRE
CLASS="PROGRAMLISTING"
>CLUSTER emp_ind ON emp
 </PRE
></DIV
><DIV
CLASS="REFSECT1"
><H2
>  Compatibility
 </H2
><P
> </P
><DIV
CLASS="REFSECT2"
><H3
>  SQL92
  </H3
><P
>  There is no <B
CLASS="COMMAND"
>CLUSTER</B
> statement in SQL92.
  </P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-close.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="user.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="sql-commit.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>CLOSE</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="sql-commands.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>COMMIT</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>