Skip to content
Snippets Groups Projects
  • Peter Eisentraut's avatar
    6ef24487
    Fix a whitespace issue with the man pages · 6ef24487
    Peter Eisentraut authored
    There is what may actually be a mistake in our markup.  The problem is
    in a situation like
    
    <para>
     <command>FOO</command> is ...
    
    there is strictly speaking a line break before "FOO".  In the HTML
    output, this does not appear to be a problem, but in the man page
    output, this shows up, so you get double blank lines at odd places.
    
    So far, we have attempted to work around this with an XSL hack, but
    that causes other problems, such as creating run-ins in places like
    
    <acronym>SQL</acronym> <command>COPY</command>
    
    So fix the problem properly by removing the extra whitespace.  I only
    fixed the problems that affect the man page output, not all the
    places.
    6ef24487
    History
    Fix a whitespace issue with the man pages
    Peter Eisentraut authored
    There is what may actually be a mistake in our markup.  The problem is
    in a situation like
    
    <para>
     <command>FOO</command> is ...
    
    there is strictly speaking a line break before "FOO".  In the HTML
    output, this does not appear to be a problem, but in the man page
    output, this shows up, so you get double blank lines at odd places.
    
    So far, we have attempted to work around this with an XSL hack, but
    that causes other problems, such as creating run-ins in places like
    
    <acronym>SQL</acronym> <command>COPY</command>
    
    So fix the problem properly by removing the extra whitespace.  I only
    fixed the problems that affect the man page output, not all the
    places.
alter_operator.sgml 3.50 KiB
<!--
doc/src/sgml/ref/alter_operator.sgml
PostgreSQL documentation
-->

<refentry id="SQL-ALTEROPERATOR">
 <refmeta>
  <refentrytitle>ALTER OPERATOR</refentrytitle>
  <manvolnum>7</manvolnum>
  <refmiscinfo>SQL - Language Statements</refmiscinfo>
 </refmeta>

 <refnamediv>
  <refname>ALTER OPERATOR</refname>
  <refpurpose>change the definition of an operator</refpurpose>
 </refnamediv>

 <indexterm zone="sql-alteroperator">
  <primary>ALTER OPERATOR</primary>
 </indexterm>

 <refsynopsisdiv>
<synopsis>
ALTER OPERATOR <replaceable>name</replaceable> ( { <replaceable>left_type</replaceable> | NONE } , { <replaceable>right_type</replaceable> | NONE } ) OWNER TO <replaceable>new_owner</replaceable>
ALTER OPERATOR <replaceable>name</replaceable> ( { <replaceable>left_type</replaceable> | NONE } , { <replaceable>right_type</replaceable> | NONE } ) SET SCHEMA <replaceable>new_schema</replaceable>
</synopsis>
 </refsynopsisdiv>

 <refsect1>
  <title>Description</title>

  <para>
   <command>ALTER OPERATOR</command> changes the definition of
   an operator.  The only currently available functionality is to change the
   owner of the operator.
  </para>

  <para>
   You must own the operator to use <command>ALTER OPERATOR</>.
   To alter the owner, you must also be a direct or indirect member of the new
   owning role, and that role must have <literal>CREATE</literal> privilege on
   the operator's schema.  (These restrictions enforce that altering the owner
   doesn't do anything you couldn't do by dropping and recreating the operator.
   However, a superuser can alter ownership of any operator anyway.)
  </para>
 </refsect1>

 <refsect1>
  <title>Parameters</title>

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

   <varlistentry>
    <term><replaceable class="parameter">left_type</replaceable></term>
    <listitem>
     <para>
      The data type of the operator's left operand; write
      <literal>NONE</literal> if the operator has no left operand.
     </para>
    </listitem>
   </varlistentry>
   <varlistentry>
    <term><replaceable class="parameter">right_type</replaceable></term>
    <listitem>
     <para>
      The data type of the operator's right operand; write
      <literal>NONE</literal> if the operator has no right operand.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term><replaceable class="parameter">new_owner</replaceable></term>
    <listitem>
     <para>
      The new owner of the operator.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term><replaceable class="parameter">new_schema</replaceable></term>
    <listitem>
     <para>
      The new schema for the operator.
     </para>
    </listitem>
   </varlistentry>
  </variablelist>
 </refsect1>

 <refsect1>
  <title>Examples</title>

  <para>
   Change the owner of a custom operator <literal>a @@ b</literal> for type <type>text</type>:
<programlisting>
ALTER OPERATOR @@ (text, text) OWNER TO joe;
</programlisting></para>
 </refsect1>

 <refsect1>
  <title>Compatibility</title>

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

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

  <simplelist type="inline">
   <member><xref linkend="sql-createoperator"></member>
   <member><xref linkend="sql-dropoperator"></member>
  </simplelist>
 </refsect1>
</refentry>