From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Jason Tishler <jason(at)tishler(dot)net>, pgsql-cygwin(at)postgresql(dot)org, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] ipc-daemon |
Date: | 2002-11-06 00:12:24 |
Message-ID: | 4619.1036541544@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cygwin pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> I disagree: just because cygipc returns error codes chosen at random
>> doesn't mean that we should neglect the clear meaning of an error code.
>> If a normal Unix system were to return EACCES here, the clear
>> implication would be that there is an existing segment that we do not
>> have permission to access.
> OK, but shouldn't the looping for a new segment terminate sometime? As it
> stands it will wrap around and run forever.
Hm. It would be reasonable to put a limit on the number of attempts,
probably. (There's a similar limit on attempts to create a lockfile.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Cornelia Boenigk | 2002-11-06 00:42:20 | Re: Postmaster will not start |
Previous Message | Peter Eisentraut | 2002-11-05 18:11:38 | Re: [HACKERS] ipc-daemon |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2002-11-06 00:13:30 | Re: PL/Perl and Perl 5.8 |
Previous Message | Robert E. Bruccoleri | 2002-11-06 00:11:31 | Re: Test of PG7.3.2b2 on SGI Irix |