| From: | award(at)dominionsciences(dot)com |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | award(at)dominionsciences(dot)com, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: syslog enabled causes random hangs? |
| Date: | 2003-07-30 18:21:02 |
| Message-ID: | 12388.68.62.129.152.1059589262.squirrel@www.dominionsciences.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> It's really too bad that your gdb backtrace didn't show anything past
> the write_syslog level (which is an elog subroutine). If we could see
> whether the elog had been issued from a signal handler, and if so what
> it had interrupted, we'd have an idea whether this is a known syslog
> deficiency or not. Do you want to rebuild with debug symbols and try
> the backtrace again?
Since you think it might be necessary to add a workaround in Postgresql,
I'll try it again when I install 7.3.4 on my test machine. That will
probably be in a few days. I need to get back to real work again. :-)
I'm sure I rebuilt 7.3.3 with the symbols left in place. Off the top of
your head do you know an easy way to tell if a binary still has symbols?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tech techie | 2003-07-30 19:15:38 | Re: LargeObjectDrop and simple_heap_delete - Are these errors normal? |
| Previous Message | Andrew Sullivan | 2003-07-30 17:40:55 | Re: PG 7.3.3 startup problem |