head	1.3;
access;
symbols
	REL9_0_0:1.3
	REL9_1_ALPHA1:1.3
	REL9_0_RC1:1.3
	REL9_0_BETA4:1.3
	REL9_0_STABLE:1.3.0.2
	REL9_0_BETA3:1.3
	REL9_0_BETA2:1.3
	REL8_3_11:1.1
	REL8_4_4:1.2
	REL9_0_BETA1:1.3
	REL9_0_ALPHA5_BRANCH:1.2.0.12
	REL9_0_ALPHA5:1.2
	REL8_3_10:1.1
	REL8_4_3:1.2
	REL9_0_ALPHA4:1.2
	REL9_0_ALPHA4_BRANCH:1.2.0.10
	REL8_5_ALPHA3:1.2
	REL8_5_ALPHA3_BRANCH:1.2.0.8
	REL8_3_9:1.1
	REL8_4_2:1.2
	REL8_5_ALPHA2:1.2
	REL8_5_ALPHA2_BRANCH:1.2.0.6
	REL8_3_8:1.1
	REL8_4_1:1.2
	REL8_5_ALPHA1:1.2
	REL8_5_ALPHA1_BRANCH:1.2.0.4
	REL8_4_STABLE:1.2.0.2
	REL8_4_0:1.2
	REL8_4_RC2:1.2
	REL8_4_RC1:1.2
	REL8_4_BETA2:1.2
	REL8_4_BETA1:1.2
	REL8_3_7:1.1
	REL8_3_6:1.1
	REL8_3_5:1.1
	REL8_3_4:1.1
	REL8_3_3:1.1
	REL8_3_2:1.1
	REL8_3_1:1.1
	REL8_3_STABLE:1.1.0.2
	REL8_3_0:1.1
	REL8_3_RC2:1.1
	REL8_3_RC1:1.1
	REL8_3_BETA4:1.1
	REL8_3_BETA3:1.1
	REL8_3_BETA2:1.1
	REL8_3_BETA1:1.1;
locks; strict;
comment	@# @;


1.3
date	2010.04.03.07.23.01;	author petere;	state Exp;
branches;
next	1.2;

1.2
date	2008.11.14.10.22.46;	author petere;	state Exp;
branches;
next	1.1;

1.1
date	2007.01.23.05.07.17;	author tgl;	state Exp;
branches;
next	;


desc
@@


1.3
log
@Remove unnecessary xref endterm attributes and title ids

The endterm attribute is mainly useful when the toolchain does not support
automatic link target text generation for a particular situation.  In  the
past, this was required by the man page tools for all reference page links,
but that is no longer the case, and it now actually gets in the way of
proper automatic link text generation.  The only remaining use cases are
currently xrefs to refsects.
@
text
@<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/drop_opfamily.sgml,v 1.2 2008/11/14 10:22:46 petere Exp $
PostgreSQL documentation
-->

<refentry id="SQL-DROPOPFAMILY">
 <refmeta>
  <refentrytitle>DROP OPERATOR FAMILY</refentrytitle>
  <manvolnum>7</manvolnum>
  <refmiscinfo>SQL - Language Statements</refmiscinfo>
 </refmeta>

 <refnamediv>
  <refname>DROP OPERATOR FAMILY</refname>
  <refpurpose>remove an operator family</refpurpose>
 </refnamediv>
  
 <indexterm zone="sql-dropopfamily">
  <primary>DROP OPERATOR FAMILY</primary>
 </indexterm>

 <refsynopsisdiv>
<synopsis>
DROP OPERATOR FAMILY [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> USING <replaceable class="PARAMETER">index_method</replaceable> [ CASCADE | RESTRICT ]
</synopsis>
 </refsynopsisdiv>

 <refsect1>
  <title>Description</title>

  <para>
   <command>DROP OPERATOR FAMILY</command> drops an existing operator family.
   To execute this command you must be the owner of the operator family.
  </para>

  <para>
   <command>DROP OPERATOR FAMILY</command> includes dropping any operator
   classes contained in the family, but it does not drop any of the operators
   or functions referenced by the family.  If there are any indexes depending
   on operator classes within the family, you will need to specify
   <literal>CASCADE</> for the drop to complete.
  </para>
 </refsect1>
  
 <refsect1>
  <title>Parameters</title>

  <variablelist>

   <varlistentry>
    <term><literal>IF EXISTS</literal></term>
    <listitem>
     <para>
      Do not throw an error if the operator family does not exist.
      A notice is issued in this case.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term><replaceable class="parameter">name</replaceable></term>
    <listitem>
     <para>
      The name (optionally schema-qualified) of an existing operator family.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term><replaceable class="parameter">index_method</replaceable></term>
    <listitem>
     <para>
      The name of the index access method the operator family is for.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term><literal>CASCADE</literal></term>
    <listitem>
     <para>
      Automatically drop objects that depend on the operator family.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term><literal>RESTRICT</literal></term>
    <listitem>
     <para>
      Refuse to drop the operator family if any objects depend on it.
      This is the default.
     </para>
    </listitem>
   </varlistentry>
  </variablelist>
 </refsect1>

 <refsect1>
  <title>Examples</title>

  <para>
   Remove the B-tree operator family <literal>float_ops</literal>:

<programlisting>
DROP OPERATOR FAMILY float_ops USING btree;
</programlisting>

   This command will not succeed if there are any existing indexes
   that use operator classes within the family.  Add <literal>CASCADE</> to
   drop such indexes along with the operator family.
  </para>
 </refsect1>
 
 <refsect1>
  <title>Compatibility</title>

  <para>
   There is no <command>DROP OPERATOR FAMILY</command> statement in the
   SQL standard.
  </para>
 </refsect1>

 <refsect1>
  <title>See Also</title>

  <simplelist type="inline">
   <member><xref linkend="sql-alteropfamily"></member>
   <member><xref linkend="sql-createopfamily"></member>
   <member><xref linkend="sql-alteropclass"></member>
   <member><xref linkend="sql-createopclass"></member>
   <member><xref linkend="sql-dropopclass"></member>
  </simplelist>
 </refsect1>

</refentry>
@


1.2
log
@Set SQL man pages to be section 7 by default, and only transform them to
another section if required by the platform (instead of the old way of
building them in section "l" and always transforming them to the
platform-specific section).

This speeds up the installation on common platforms, and it avoids some
funny business with the man page tools and build process.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/ref/drop_opfamily.sgml,v 1.1 2007/01/23 05:07:17 tgl Exp $
d8 1
a8 1
  <refentrytitle id="SQL-DROPOPFAMILY-TITLE">DROP OPERATOR FAMILY</refentrytitle>
d128 5
a132 5
   <member><xref linkend="sql-alteropfamily" endterm="sql-alteropfamily-title"></member>
   <member><xref linkend="sql-createopfamily" endterm="sql-createopfamily-title"></member>
   <member><xref linkend="sql-alteropclass" endterm="sql-alteropclass-title"></member>
   <member><xref linkend="sql-createopclass" endterm="sql-createopclass-title"></member>
   <member><xref linkend="sql-dropopclass" endterm="sql-dropopclass-title"></member>
@


1.1
log
@Add CREATE/ALTER/DROP OPERATOR FAMILY commands, also COMMENT ON OPERATOR
FAMILY; and add FAMILY option to CREATE OPERATOR CLASS to allow adding a
class to a pre-existing family.  Per previous discussion.  Man, what a
tedious lot of cutting and pasting ...
@
text
@d2 1
a2 1
$PostgreSQL$
d9 1
@

