Hi!
> > 2: how often should I reindex my db, are there any standards
> >or accepted practices out there
>
> I recreate my indices every week, or after any extensive updates or
> deletes. Again, I believe that 7.2 has some new stuff to deal with this
> issue.
This brings me to another point.
On Tue, Dec 18, 2001 at 11:29:02AM +0100, Florian Helmberger wrote:
> Hi!
>
> > > 2: how often should I reindex my db, are there any standards
> > >or accepted practices out there
> >
> > I recreate my indices every week, or after any extensive updates or
> > deletes. Again, I believe that 7
Phill and Glen,
We've just tracked down one mechanism that allows duplicate rows to be
spawned --- see http://fts.postgresql.org/db/mw/msg.html?mid=1078374
and following discussion. In the example given by Brian Hirt, VACUUM's
creation of a duplicate row causes a unique-key violation to be
repor
Hi,
Does postgresql have any problems managing load? I'm running a medium sized
(30k customers) ISP off a postgresql database but it can't seem to manage
very well with the dozen or so requests per second it receives. The machine
we are handling is plenty powerful enough for a database like thi
I'm afraid you'll have to provide more info than you have... For 7.1.3, what
queries are taking so long? You VACUUM'd your database often (if lots of
updates, inserts and deletes were happening, yes)?
For 7.2b4 - it shouldn't crash, but do you have any clue when it does or
what query/situation mi
On Wed, 19 Dec 2001, Daniel Andersen wrote:
> Hi,
> Does postgresql have any problems managing load? I'm running a medium sized
> (30k customers) ISP off a postgresql database but it can't seem to manage
> very well with the dozen or so requests per second it receives. The machine
> we are handl
On Wed, 19 Dec 2001, Daniel Andersen wrote:
> Does postgresql have any problems managing load? I'm running a medium sized
> (30k customers) ISP off a postgresql database but it can't seem to manage
> very well with the dozen or so requests per second it receives. The machine
> we are handling is
> > Does postgresql have any problems managing load? I'm running a medium
> > sized (30k customers) ISP off a postgresql database but it can't seem to
> > manage very well with the dozen or so requests per second it receives.
> > The machine we are handling is plenty powerful enough for a database
> Hello Daniel,
>
> I can't answer your specific question, but I _can_
> tell you that the gurus will probably need more information
> that you presented.
>
> 1) What operating system and version?
Slackware linux 8.0, with the kernel upgraded to 2.4.16, stripped to the bare
bones for effic
Daniel Andersen <[EMAIL PROTECTED]> writes:
> installed 7.2b4 only to find it runs like a dream (less that 10% cpu usage
> most of the time) but eventually fails to fork and crashes and burns,
You'll need to be a *lot* more specific than that. Log entries,
corefile backtraces, etc, please.
Daniel Andersen <[EMAIL PROTECTED]> writes:
> [4059] DEBUG: connection startup failed (fork failure): Resource
> temporarily unavailable
> [4059] DEBUG: could not launch checkpoint process (fork failure): Resource
> temporarily unavailable
Hmm ... a fork failure suggests resource exhaustion som
> sort_mem = 1024
> shared_buffers = 2048 (tried higher, but didnt' seem to improve anything)
> max_connections = 300
>
> error message just comes out of the blue, the database is chugging along
> happily and then suddenly[4059] DEBUG: connection startup failed (fork
> failure): Resource tempo
On Wednesday 19 December 2001 12:10 am, Daniel Andersen wrote:
> Slackware linux 8.0, with the kernel upgraded to 2.4.16, stripped to the
> bare bones for efficiency
> [4059] DEBUG: connection startup failed (fork failure): Resource
> temporarily unavailable
> there are generally up to 200 co
13 matches
Mail list logo
