Re: Have psql show current sequnce values - (Resubmission)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Dhanaraj M <Dhanaraj(dot)M(at)Sun(dot)COM>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Have psql show current sequnce values - (Resubmission)
Date: 2007-02-09 01:15:53
Message-ID: 24338.1170983753@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> I think we discussed replacing the current sequence representation with
> a single relation that would contain all sequences in the database, so
> that you could do "select * from pg_sequence" and get all the values in
> one go. The idea was considered not implementable at the time due to us
> not having "non transactional relations", but I'd suggest adding it to
> the TODO so that we don't forget later.

I wonder if we could kluge it by making all sequences inheritance
children of a dummy "pg_sequence" relation. Or perhaps better,
implement this as a system view on a set-returning function --- if there
are lots of sequences the planner's not likely to help you much anyway.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-02-09 01:29:22 Re: Have psql show current sequnce values - (Resubmission)
Previous Message Bruce Momjian 2007-02-09 00:36:20 Re: Proposal: Commit timestamp

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-02-09 01:29:22 Re: Have psql show current sequnce values - (Resubmission)
Previous Message Bruce Momjian 2007-02-09 00:55:39 Re: SSL enhancement patch ver.2