On Wed, Dec 04, 2002 at 08:39:48PM +0000, Oliver Elphick wrote:
> On Wed, 2002-12-04 at 18:00, Dmitri Touretsky wrote:
>
> > One more question related to performance. I have a VERY BIG table
> > (abot 20 million records) which is accessed relatively seldom, like
> > once a day (basically, it's archived data which sometimes may be
> > needed). How this table affect performance of the database? Is it
> > worse to create another database for storing this data, and keep the
> > main DB small?
>
> It will make no difference to performance except when it is being used.
True. But you might want to separate them if it will make it more
flexible for you (being able to dump all of the smaller database and
move it to a different machine, etc.) But if you separate them, it will
be harder to do cross-database queries (but see dblink/ in contrib for a
solution). All things being equal, I'd probably keep them together.
--
Joel BURTON | joel@joelburton.com | joelburton.com | aim: wjoelburton
Independent Knowledge Management Consultant
