Обсуждение: Re: 7.1 ... wtf?

I'm assuming you've read the manual carefully.

Please make doubley sure you configured PostrgreSQL and your system
properly. Server runtime enviroment comes to mind.

Check the error logs, its hard to beleive you are getting such blow ups with
absolutly nothing in any of the logs.

Have you turned on the most verbose loging so you can see all the
transactions on your system? Be suprising if you are still getting nothing.

If you think performance is bad as hell, and it's clearly not a
configuration or user issue (ie, pgsql is at fault), consider writing up a
proper bug report. The fact that a good number of folks successfully use
pgsql for larger installations argues I think for a configuration issue, but
it could certainly be a bug somewhere.

AZ

AZ









"Thomas Heller" <maniax@comtron.net> wrote in message
news:9dbkpq$1d9a$1@news.tht.net...
> Hi again,
>
> sometime ago i had a post on 7.1 performance .. this is still up-to-date
> cause the performance is bad like hell but i have a little bit bigger
> problem now. I have a dual p3-1ghz + 1gig ram. The hardware is new (asus
> dual board + registered ecc sdram) and is quite nice but postgres7.1 seems
> to mess up with it. I have no idea why, but the server kills himself every
> now and then. the load goes up to 50 and then some minutes later its gone
> (doesn't respond to ANY cmds, no ssh, no shell). i always have to reset
it.
> the only thing i found pointing me towards postgres are these error
messages
> when surfing the pages which use the server as backend.
>
> I get these errors in a random manner:
>
> The System is in maintenance mode (something like that)
> The System is in recovery state
> The System is shutting down.
> The System is going up.
> Sorry, to many clients already (2 processes running / 64 max connections
> configured)
>
> Note: I do not restart the postmaster nor does any script. the system is
> started and running .. why does he say "shutting down"?!! also the
> performance seems to be really crap. (the database is currenly 80mb
nothing
> THIS server should worry about).
>
> any help?
>
> thank,
> thomas
>
>

Hi,

hmm I don't know if I'm right but I think when I run the postmaster with
default values configured it should run at least in a acceptable manner. But
it does not. Also it does not respond to any minor tweaks like increasing
wal-buffers, wal-files, sort-mem, etc. ... Its just doing his weird actions
and performance is quite bad. I upgraded to 7.1.1 yesterday and i hope it
will survive today without any major problems. Looks good yet.

Also I would greatly appreciate any help concerning configuration options
etc. ...

cu
mx

"August Zajonc" <augustz@bigfoot.com> wrote in message
news:9dc883$1h9g$1@news.tht.net...
> I'm assuming you've read the manual carefully.
>
> Please make doubley sure you configured PostrgreSQL and your system
> properly. Server runtime enviroment comes to mind.
>
> Check the error logs, its hard to beleive you are getting such blow ups
with
> absolutly nothing in any of the logs.
>
> Have you turned on the most verbose loging so you can see all the
> transactions on your system? Be suprising if you are still getting
nothing.
>
> If you think performance is bad as hell, and it's clearly not a
> configuration or user issue (ie, pgsql is at fault), consider writing up a
> proper bug report. The fact that a good number of folks successfully use
> pgsql for larger installations argues I think for a configuration issue,
but
> it could certainly be a bug somewhere.
>
> AZ