Also you should check for any CPU malfunction, overheating, etc..
and for motherboard problems as well, power supply, etc...
Anyway, your problem is not postgresql (postgresql does not delete its own
files).
Your problem is below your OS and everything that comes underneath.
What do the linux log
Not sure what you mean.
Once we start getting that error in the postgres log, there is no autovacuum
entry. Only that error message once every minute (and as i wrote in my last
email, the same message all the time).
The question is what is causing postgres to stop working. Autovacuum or
another r
Thanks Scott
In fact checking the application there are a lots of queries that doesn't make
the conversion, in order to temporally skip this issue,I like to try to import
those conversions from the 8.1 version to the actual postgres, how can I do
that?
Octavio
--- El mar, 11/16/10, Scott Marl
Excerpts from Pablo Delgado Díaz-Pache's message of mar nov 16 12:18:09 -0300
2010:
> Not sure what you mean.
>
> Once we start getting that error in the postgres log, there is no autovacuum
> entry. Only that error message once every minute (and as i wrote in my last
> email, the same message al
I'm having the same problem - and have checked the application log and yes
the problem seems to be that postgres user doesn't have permission to write
postmaster.pid file. What is the solution to this?
Regards
Tracey
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make
"Tracey Osborne" writes:
> I'm having the same problem - and have checked the application log and yes
> the problem seems to be that postgres user doesn't have permission to write
> postmaster.pid file. What is the solution to this?
Did you run initdb as the postgres user? Seems like you migh
