Re: Serials.

From: Grant <grant(at)conprojan(dot)com(dot)au>
To: Dan Lyke <danlyke(at)flutterby(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Serials.
Date: 2001-03-25 23:58:57
Message-ID: Pine.LNX.4.21.0103260954540.29634-100000@webster.conprojan.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

> Grant writes:
> > I have a message board. Where users can send each other messages. I
> > doubt I will ever get 2147483647 messages, but I want to make sure I
> > never get an error where the message isn't sent.
>
> Think about loads. If your users are going to be posting 10
> messages/second, that's 864000 messages per day, you won't wrap for
> nearly 7 years. I've got a pretty heavy mail load, including spam I
> probably get 300 messages/day, weekends are lighter, so if you've got
> a bunch of weenies who are subscribed to a gazillion mailing lists
> you're talking three thousand users for six and a half years.
>
> A little light if you're planning on being the next Hotmail (A test
> account set up there gets 70 spams/day without my ever publishing the
> address), but for your average mid-range discussion forum you're
> probably good for a while. I doubt that, say, Salon's TableTalk forum
> gets even 10k new messages per day.

I understand what you're saying. However it's not the amount of messages per day. I have cycle set on the sequence so that when it reaches the limit it will start back at 1 again. If however some users still have messages in their accounts that have used random ids from 1 onwards postgresql will produce the error that it's trying to insert a duplicate id that already exists, so in theory I want the system to run for infinity. I hope this makes sense. Thankyou for your time.

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Jack 2001-03-26 00:10:41 about raise exception
Previous Message Tom Lane 2001-03-25 21:14:51 Re: CHAR or VARCHAR