Bruce Momjian said:
> Tom Lane wrote:
>> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>> > Second attempt attached. The fatal message now reads "no configured
>> > listening socket available", but I am not wedded to the wording. I
>> > also was not sure how to mark up * in the docs.
>>
>> I went wit
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
> Both of these are not always correct - they might well have configured a
> listening address but we were unable to bind to it, although in that case
> a warning would have already been issued. To be strictly correct either we
> need to use a flag to di
Tom Lane wrote:
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
Both of these are not always correct - they might well have configured a
listening address but we were unable to bind to it, although in that case
a warning would have already been issued. To be strictly correct either we
need to use
Tom Lane wrote:
> "Andrew Dunstan" <[EMAIL PROTECTED]> writes:
> > Both of these are not always correct - they might well have configured a
> > listening address but we were unable to bind to it, although in that case
> > a warning would have already been issued. To be strictly correct either we
>
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> How about "no socket created for listening" or some such?
> Or "no socket available for listening"?
"Created" seems better since it's a verb, and focuses attention on the
probability that we tried and failed to make a socket. "Availa
Alvaro Herrera wrote:
> On Mon, Dec 01, 2003 at 05:07:40PM -0500, Bruce Momjian wrote:
>
> > Neil Conway wrote:
> > > This patch adds a new GUC var, "default_use_oids", which follows the
> > > proposal for eventually deprecating OIDs on user tables that I posted
> > > earlier to pgsql-hackers. pg_
For application to HEAD, following community review.
Supplement to previous win32 patch for dfmgr. Win32 replacement for
configure time constants like PKGLIBDIR.
---
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies se
For application to HEAD.
This should take care of most, if not all, cases where a backend can be
interrupted in a blocking socket operation by a signal which itself performs
a socket operation (which interacts badly with our APC-based signal
implementation).
---
Certain disclaimers and policies
