Re: Requirements for a database server

From: Robert(dot)Farrugia(at)go(dot)com(dot)mt
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org, Ragnar Kjørstad <postgres(at)ragnark(dot)vestdata(dot)no>
Subject: Re: Requirements for a database server
Date: 2001-07-20 05:26:43
Message-ID: OF6EC329A4.DD1FE91F-ONC1256A8F.001DCFD0@go.com.mt
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


I will try and do this. Will let you know how it went.

Regards
Robert


Tom Lane
<tgl(at)sss(dot)pgh(dot) To: Ragnar Kjørstad <postgres(at)ragnark(dot)vestdata(dot)no>
pa.us> cc: Robert(dot)Farrugia(at)go(dot)com(dot)mt, pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Requirements for a database server
19/07/2001
20:08

=?iso-8859-1?Q?Ragnar_Kj=F8rstad?= <postgres(at)ragnark(dot)vestdata(dot)no> writes:
> On Thu, Jul 19, 2001 at 07:38:25AM +0200, Robert(dot)Farrugia(at)go(dot)com(dot)mt
wrote:
>> Since I have a number of heavy inserts per day, dropping the indexes and
>> recreating them could be an option. Only problem I see is that to
>> recreate them they take alot of time, at which queries will be
tremendously
>> slow.

> What about first creating new indexes (with a different name), and then
> delete the old one? will that work?

Should work fine as far as read-only queries go. CREATE INDEX locks out
writes, however, so those will be blocked in any case...

regards, tom lane

Browse pgsql-admin by date

  From Date Subject
Next Message Mike Marconi 2001-07-20 15:22:33 starting server problem
Previous Message Alexey Rodriguez Yakushev 2001-07-20 00:45:05 High load