Re: pgsql/src/backend/commands sequence.c - Mailing list pgsql-committers

From Bruce Momjian
Subject Re: pgsql/src/backend/commands sequence.c
Date
Msg-id 200201112047.g0BKlXx14796@candle.pha.pa.us
Whole thread Raw
In response to Re: pgsql/src/backend/commands sequence.c  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Oh.  Is that good?  If we set the sequence xid as frozen, how do we
> > rollback a sequence creation?
>
> If we roll back a sequence creation, the whole table goes away.
> Conversely, even if we commit, no one can see the sequence until they
> can see the pg_class entry for it.  Thus, it doesn't matter what's in
> the tuple.

OK, so you are using the pg_class visibility/destuction as an
optimitation to prevent vacuum of sequences  --- sounds fine.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql/src/backend/commands sequence.c
Next
From: tgl@postgresql.org
Date:
Subject: pgsql/contrib/pg_resetxlog README.pg_resetxlog ...