| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave(at)micro-automation(dot)net |
| Cc: | "'# sriram #'" <sriram(at)imsc(dot)ernet(dot)in>, "'Nick'" <nickf(at)ontko(dot)com>, "'Psql-Jdbc'" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Strange Error |
| Date: | 2002-02-26 15:25:49 |
| Message-ID: | 29822.1014737149@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
"Dave Cramer" <Dave(at)micro-automation(dot)net> writes:
> ... My assumption is that something is
> restarting postgres? I suspect that it will drop at exactly the same
> time everyday. At any rate, I don't believe it is the jdbc driver, or
> postgres. I routinely keep connections alive for months.
> One thing that just hit me, do you do a Vacuum in a cron job? Of course
> that would only affect postgres, but it popped in my head.
Another possibility, since postgres is normally run as an unprivileged
user, is that the server is being killed because it's exceeding some
"ulimit" setting. Cure: set limit to unlimited before starting
postmaster. Not sure if mysql is vulnerable to same thing (don't they
prefer to run as root?)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-02-26 15:55:41 | Re: Timestamp output |
| Previous Message | Peter V. Cooper | 2002-02-26 15:03:05 | Re: Strange Error |