| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Radosław Smogura <rsmogura(at)softperience(dot)eu> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Crash dumps |
| Date: | 2011-07-07 14:22:28 |
| Message-ID: | 29881.1310048548@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?utf-8?q?Rados=C5=82aw_Smogura?= <rsmogura(at)softperience(dot)eu> writes:
> Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> Thursday 07 of July 2011 01:05:48
>> How do you propose to make that reliable, though?
> I want to add IPC layer to postgresql, few approches may be considerable,
> 1. System IPC
> 2. Urgent data on socket
> 3. Sockets (at least descriptors) + threads
> 4. Not portable, fork in segfault (I think forked process should start in
> segfault too).
An IPC layer to be invoked during segfaults? Somehow I don't think
that's going to pass the reliability threshold. It doesn't sound
promising from a portability standpoint either, since not one of your
suggestions will work everywhere, even without the already-segfaulted
context to worry about.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-07-07 14:24:49 | Re: Expression Pruning in postgress |
| Previous Message | Magnus Hagander | 2011-07-07 11:13:45 | Re: Moving the community git server |