If you've got connections randomly closing, it's also likely you have
flakey memory or hardware. www.memtest86.com is a good tester.
Postgresql is good, but it can't make up for broken hardware. And broken
hardware is way more common than most people think.
On Fri, 2 May 2003, Erik Ronström wrote:
> --- Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > You're going to need to provide a self-contained example, or else a
> > stack trace. [...]
>
> I'm quite a beginner of pgsql, and there are some things I don't know:
> - How do I print a stack trace?
> - Is there a log file somewhere which is more extensive than the
> outputted DEBUG and NOTICE messages?
>
> BTW, I realized that the errors seem to appear randomly; I tried to run
> the function several times with the same parameters, and it seems to
> work about half of the times.
>
> I'm using version 7.2.1, and I saw somewhere that it may be buggy. Can
> it be a bug? Should I upgrade to 7.2.3?
>
> Thanks for your answer
> Erik
>
> __________________________________________________
> Yahoo! Plus
> For a better Internet experience
> http://www.yahoo.co.uk/btoffer
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
