Thread: Doc update: ALTER SEQUENCE name RENAME TO can be rolled back

--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com
Index: doc/src/sgml/ref/alter_sequence.sgml
===================================================================
RCS file: /home/hlinnaka/pgcvsrepository/pgsql/doc/src/sgml/ref/alter_sequence.sgml,v
retrieving revision 1.17
diff -c -r1.17 alter_sequence.sgml
*** doc/src/sgml/ref/alter_sequence.sgml    3 Jul 2007 01:30:35 -0000    1.17
--- doc/src/sgml/ref/alter_sequence.sgml    3 Oct 2007 09:33:38 -0000
***************
*** 224,230 ****
     same sequence, <command>ALTER SEQUENCE</command>'s effects on the sequence
     generation parameters are never rolled back;
     those changes take effect immediately and are not reversible.  However,
!    the <literal>OWNED BY</> and <literal>SET SCHEMA</> clauses are ordinary
     catalog updates and can be rolled back.
    </para>

--- 224,230 ----
     same sequence, <command>ALTER SEQUENCE</command>'s effects on the sequence
     generation parameters are never rolled back;
     those changes take effect immediately and are not reversible.  However,
!    the <literal>OWNED BY</>, <literal>SET SCHEMA</> and <literal>RENAME</> clauses are ordinary
     catalog updates and can be rolled back.
    </para>

Heikki Linnakangas <heikki@enterprisedb.com> writes:
>      those changes take effect immediately and are not reversible.  However,
> !    the <literal>OWNED BY</> and <literal>SET SCHEMA</> clauses are ordinary
>      catalog updates and can be rolled back.

>      those changes take effect immediately and are not reversible.  However,
> !    the <literal>OWNED BY</>, <literal>SET SCHEMA</> and <literal>RENAME</> clauses are ordinary
>      catalog updates and can be rolled back.

Good catch --- applied along with some other fixes.

            regards, tom lane