Periodically we have queries (can't log in to see which ones) that kill
our machine by consuming huge amounts of resource. I thought that I had
fixed this by writing a cron job that vacuums all the databases every
night, but today our machine froze again.
We run PG on Linux, for the machine in
Bradley Kieser <[EMAIL PROTECTED]> writes:
> Periodically we have queries (can't log in to see which ones) that kill
> our machine by consuming huge amounts of resource.
The first thing you need to do is find out what they are so you can fix
them. Turning on logging of all statements would be a
Hi,
I have about 35 servers running Postgresql. On one of my older ones, which just
serves up old data with no new data being added,
and running on redhat 7.3 with postgresql 7.2.4, I am getting repeated episodes
of the database shutdown while the system is still up. I find this very
unusual.
Mitchell Laks <[EMAIL PROTECTED]> writes:
> When I log in to the machine and I run pg_ctl start I get the message
> input in flex scanner failed
> and the Postgresql database system does not start up. :(.
That seems a tad impossible :-(.
Where did you come by this Postgres build exactly --- is it
