Re: [HACKERS] Problem after removal of exec(), help

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: goran(at)bildbasen(dot)se (Goran Thyni)
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Problem after removal of exec(), help
Date: 1998-06-23 15:29:28
Message-ID: 199806231529.LAA13884@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce,
> I have not look into it the specifics yet,
> but I suggest looking into what is done when
> the child process exits.
> This (the pg_exit() et al.) caused some bugs
> when we introduced unix domain sockets and
> it is not the first place one looks. :-(

Are you suggesting that because one of the backends did not exit
cleanly, that there is some problem?

Because the postmaster is resetting all shared memory at that point, I
am not sure that is the area. I have been thinking about it, and my
guess is that one of the initialization functions (lock?) just appends
to the lock queue on restart, instead of clearing it first, and a
backend that does exec() starts out with clean global variables, which
they now do not.

--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 1998-06-23 18:10:29 I thought we had fixed this for v6.3.2 ...?
Previous Message Goran Thyni 1998-06-23 11:11:26 Re: [HACKERS] Problem after removal of exec(), help