If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to pgsql-ports(at)postgresql(dot)org(dot)

To report any other bug, fill out the form below and e-mail it to
pgsql-bugs(at)postgresql(dot)org(dot)

If you not only found the problem but solved it and generated a patch
then e-mail it to pgsql-patches(at)postgresql(dot)org instead. Please use the
command "diff -c" to generate the patch.

You may also enter a bug report at http://www.postgresql.org/ instead of
e-mail-ing this form.

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : David Secret
Your email address : secret(at)kearneydev(dot)com

System Configuration
---------------------
Architecture (example: Intel Pentium) : AMD K6-200

Operating System (example: Linux 2.0.26 ELF) : Linux 2.0.36 ELF/RH 5.2

PostgreSQL version (example: PostgreSQL-6.4.2) : PostgreSQL-6.4.2

Compiler used (example: gcc 2.8.0) : gcc 2.7.2.3

Please enter a FULL description of your problem:
------------------------------------------------
About once daily my visual basic 5 program crashes the backend, not only
does it crash but it <zombie>s all of the postmaster processes, I'm in the
process of writing a perl script to zap all of the zombies & restart postgres. I'm not sure how to reproduce this, but I'll work with you as best I can, here is the simple line in the pg.log(-d 3) file that seems to indicate where it died:

<Normal queries & such for about 3 megs before this>
query: SELECT "material_id" ,"name" ,"short_name" ,"legacy" FROM "material" ORDE
R BY "legacy" DESC,"name"
ProcessQuery
CommitTransactionCommand
ERROR: postmaster: StreamConnection: accept: Invalid argument
pmdie 3
SignalChildren: sending signal 15 to process 11590
SignalChildren: sending signal 15 to process 11589
proc_exit(0) [#0]
shmem_exit(0) [#0]
.. <Everything dies from here>

Is there a way to make it stop zombying the postmaster processes so I can just restart it from inittab? Think it's the fault of the ODBC driver? It's version 6.40.0004 ...

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------

Sigh, I'm not sure what part of my VB program does it, and no part does it reliably... It seems to be almost random. I can do one thing that crashes it, restart the DB go back and do it again and all is well.

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------

It would certainly help if the postmaster process wasn't <zombie>'d, that way I could at least restart it instantly from inittab... As to how to fix it I'll try to help as much as I can, just tell me what you want, I always keep -d 3 logs, I'll keep ODBC logs as much as I can but it usually crashes on one of my users and not me.