Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field
Date
Msg-id 200710081801.l98I1Uf28378@momjian.us
Whole thread Raw
In response to Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane wrote:
> Heikki Linnakangas <heikki@enterprisedb.com> writes:
> > Well, the way it is now is just broken, so IMO we have to either fix it
> > or remove it altogether.
>
> > Since having sequence_name in there doesn't let you do anything you
> > can't do without it, and there's no easy way to fix it, I'd say let's
> > just remove it in 8.3 and do nothing in backbranches.
>
> I don't think this is a good idea.  It's removing functionality that
> works fine as long as you don't rename sequences.  Also, there's still
> the notion of someday providing a system catalog or view that shows
> parameters of all sequences, and in that view the current column set of
> an individual sequence would be what we'd want.
>
> My inclination is to leave it alone for now until we have an approach to
> providing that view, and at that time decide what to do about individual
> sequences.  If we have to change the API, then so be it, but lets do it
> just once not twice.

Added to TODO:

        o Have ALTER SEQUENCE RENAME rename the sequence name stored
          in the sequence table

          http://archives.postgresql.org/pgsql-bugs/2007-09/msg00092.php
          http://archives.postgresql.org/pgsql-bugs/2007-10/msg00007.php

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3659: should use implizit type cast in check constraint
Next
From: Tiago Daniel Jacobs
Date:
Subject: Re: BUG #3657: Performance leaks when using between of two equal dates