Re: [GENERAL] Re: Perfomance decreasing

2001-08-20 Thread Einar Karttunen

On Fri, Aug 17, 2001 at 02:09:33PM +0600, Ivan Babikov wrote:
 
  In this case, however, I think he may be understating too much.  I read
 the original question as PostgreSQL is not useful for production systems.
 Call me melodramatic if you like: you are probably right.
 
  The point, I guess, is this: it would be really useful to have a document
 somewhere that honestly described the limitations of (the current version
 of) PostgreSQL.
 
 Do you mean Postgres becomes very weak when the size of a database achieves
 1.5Gb or something close to it?
 
 Maybe this is one of typical questions, but I have heard people complaining
 that Postgres is just for quite small bases. Now we have to choose a free
 database for then inexpensive branch of our project and Interbase looks
 better at capability to work with quite big bases (up to 10-20Gb). I am not
 sure now that Postgres will work with bases greater than 10Gb, what does All
 think?
 
 Thanks in advance, Ivan Babikoff.
 
In my experience postgresql has no problems with big databases. I have had several
problems but they had to do with the os and hardware not the db. 

- Einar Karttunen

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html



Re: [GENERAL] Re: Perfomance decreasing

2001-08-20 Thread Denis Perchine

On Friday 17 August 2001 15:09, Ivan Babikov wrote:
  In this case, however, I think he may be understating too much.  I read

 the original question as PostgreSQL is not useful for production systems.
 Call me melodramatic if you like: you are probably right.

  The point, I guess, is this: it would be really useful to have a document

 somewhere that honestly described the limitations of (the current version
 of) PostgreSQL.

 Do you mean Postgres becomes very weak when the size of a database achieves
 1.5Gb or something close to it?

 Maybe this is one of typical questions, but I have heard people complaining
 that Postgres is just for quite small bases. Now we have to choose a free
 database for then inexpensive branch of our project and Interbase looks
 better at capability to work with quite big bases (up to 10-20Gb). I am not
 sure now that Postgres will work with bases greater than 10Gb, what does
 All think?

I do not see any problems. It works for me, and I have no problems. The only 
problem you could have is with vacuum. It is solvable anyway. But if you have 
not so much updates it is not an issue too (I mean if do not update more than 
25% of DB each day).

Actually for anyone listening for such advices I would recommend to create a 
test installation, and stress test it before go to production. Interbase has 
its own problems.

-- 
Sincerely Yours,
Denis Perchine

--
E-Mail: [EMAIL PROTECTED]
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
--

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]



[GENERAL] Re: Perfomance decreasing

2001-08-14 Thread Allan Engelhardt

Tom Lane wrote:

  I'm  doing  vacuum  periodically  (once a hour), but perfomance
  still falls down.

 It sounds to me like you may be running into index growth problems.
 VACUUM is presently not good about shrinking indexes.

I always enjoy Tom's comments - he is the master of understatement and always helpful.

In this case, however, I think he may be understating too much.  I read the original 
question as PostgreSQL is not useful for production systems.  Call me melodramatic 
if you like: you are probably right.

The point, I guess, is this: it would be really useful to have a document somewhere 
that honestly described the limitations of (the current version of) PostgreSQL.  Don't 
use inheritance, don't use on 24x7 systems, whatever.  It doesn't have to be fancy 
formatting, a brain-dump to a text file would be excellent  (This is a hint, Tom 
et al!! :-))

  If you drop
 and recreate the indexes used by your most important queries, does
 the performance go back to where it was?

For what it's worth: I observed a similar issue and found that a dump and restore of 
all the databases helped.  I haven't tried just recreating the index.  I'll try it out 
and maybe post a test script to reproduce the issue. (where?)


--- Allan.



---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://www.postgresql.org/search.mpl