Filter:

Messages on November 26, 2010

Threads19 messages
8Started
3Replied in own
8Replied to othersin 4 threads
Patchesof which 3 carried a patch
1New patchfirst in its thread
2Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)[PATCH] Fix documentation about PL/Python exception handlingover 15 years ago
Replied (other)duplicate connection failure messagesover 15 years ago
Replied (other)pgsql: Fix portability issues in new src/port/inet_net_ntop.c file.over 15 years ago
Replied (other)duplicate connection failure messagesover 15 years ago
Started threadpgsql: Add inet_net_ntop.c as needed by MSVC, per Magnus.over 15 years ago
Replied (other)BUG #5650: Postgres service showing as stopped when in fact it is runningover 15 years ago
Replied (other)Follow-up patchduplicate connection failure messagesover 15 years ago
Started threadpgsql: Use conn->raddr consistently for non-connect libpq error reportiover 15 years ago
Replied (other)duplicate connection failure messagesover 15 years ago
Replied (other)Follow-up patchduplicate connection failure messagesover 15 years ago
Started threadpgsql: Update comment that says we only report last libpq connection faover 15 years ago
Started threadpgsql: Use only addr_cur when reporting connection failures in libpq.over 15 years ago
Started threadFirst patchlibpq/Makefile cleanup abandonedover 15 years ago
Started threadpgsql: Abandon use of Makefile variables in libpq/Makefile because MSVCover 15 years ago
Replied (own)pgsql: Improve pg_ctl "cannot connect" warning, per suggestion from Magover 15 years ago
Started threadpgsql: In libpq/Makefile, merge PERM_PGPORT and OPT_PGPORT into a singlover 15 years ago
Started threadpgsql: Improve pg_ctl "cannot connect" spacing, per Tom, and wording.over 15 years ago
Replied (own)pgsql: Improve pg_ctl "cannot connect" warning, per suggestion from Magover 15 years ago
Replied (own)pgsql: Improve pg_ctl "cannot connect" warning, per suggestion from Magover 15 years ago