Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: number of tables limited over time (not simultaneous)?
- From: Richard Huxton <dev(at)archonet(dot)com>
- To: dave crane <lists(at)slipt(dot)net>
- Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
- Subject: Re: number of tables limited over time (not simultaneous)?
- Date: Wed, 21 Feb 2007 09:36:03 +0000
- Message-id: <45DC1283(dot)5050807(at)archonet(dot)com>
dave crane wrote:
We've settled upon a method for gathering raw statistics from widely scattered data centers of creating one sequence per-event, per minute.
Aside from security concerns, did we miss something? Should I be worried we're going through ~60,000 sequences per day?
Well, you'll want to make sure you're vacuuming the system tables regularly. And you might want to make sure your code can retry creating the sequences once OIDs wrap around.
Not sure I'd have thought of doing things this way - I'd probably have totalled figures outside the database and then summarised them once a minute.
-- Richard Huxton Archonet Ltd
- References:
- number of tables limited over time (not simultaneous)?
- From: dave crane
- number of tables limited over time (not simultaneous)?
- Prev by Date: Re: REVOKE ALL
- Next by Date: Re: Odd behaviour of timestamptz
- Previous by thread: number of tables limited over time (not simultaneous)?
- Next by thread: Nice article on Unicode and it's encodings (utf8, utf16 and utf32)
- Indexes: