Re: SEQUENCEs and NO MAXVALUE NO MINVALUE

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Rod Taylor <rbt(at)rbt(dot)ca>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: SEQUENCEs and NO MAXVALUE NO MINVALUE
Date: 2003-02-03 15:23:28
Message-ID: 200302031523.h13FNSE20027@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


Your patch has been added to the PostgreSQL unapplied patches list at:

http://momjian.postgresql.org/cgi-bin/pgpatches

I will try to apply it within the next 48 hours.

---------------------------------------------------------------------------

Tom Lane wrote:
> Rod Taylor <rbt(at)rbt(dot)ca> writes:
> > Adds in NO MAXVALUE and NO MINVALUE options for create sequence per 200X
> > spec, which will also make alter sequence a touch easier.
>
> What are these supposed to do exactly? There is no such animal as a
> sequence that hasn't got a maxvalue, nor one without a minvalue.
> "Large" does not mean "unlimited".
>
> I'm not eager to pick up evidently-poorly-thought-out features from a
> draft spec that is nowhere near being frozen. Anyway, didn't we decide
> that converging syntax with 200X was a bad idea if we weren't going to
> converge semantics?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-02-03 15:25:43 Re: SEQUENCEs and NO MAXVALUE NO MINVALUE
Previous Message Tom Lane 2003-02-03 15:17:44 Re: targetlist functions part 1 (was [HACKERS] targetlist