Filter:

Messages on July 15, 2007

Threads20 messages
16Started
1Replied in own
3Replied to othersin 3 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Started threadpgsql: Get rid of overly cute, unportable, probably not very efficientabout 19 years ago
Started threadpgsql: Fix CHECK_RELATION_BLOCK_RANGE macro, which was not merelyabout 19 years ago
Started threadpgsql: Fix CHECK_RELATION_BLOCK_RANGE macro, which was not merelyabout 19 years ago
Started threadpgsql: Fix a passel of signed vs unsigned char warnings.about 19 years ago
Started threadpgsql: Silence a rather odd compiler warning.about 19 years ago
Started threadpgsql: Silence a rather odd compiler warning.about 19 years ago
Started threadpgsql: Avoid possibly-unportable initializer, per buildfarm warning.about 19 years ago
Started threadpgsql: Change a couple of exit(0) to return 0 to suppress complaintsabout 19 years ago
Started threadpgsql: Silence Solaris compiler warnings, per buildfarm.about 19 years ago
Started threadpgsql: Silence Solaris compiler warning, per buildfarm.about 19 years ago
Started threadpgsql: Fix compile warning on Solaris, per buildfarm.about 19 years ago
Started threadpgsql: Fix possible portability problem, per buildfarm warnings.about 19 years ago
Started threadpgsql: Fix unportable use of isspace(), per buildfarm results.about 19 years ago
Replied (other)compiler warnings on the buildfarmabout 19 years ago
Started threadpgsql: Because plpgsql's scanner uses %option case-insensitive, flex'sabout 19 years ago
Replied (other)pg_dump ignore tablespacesabout 19 years ago
Replied (other)Warning for exceeding max locks?about 19 years ago
Started threadpgsql: Reject zero or negative BY step in plpgsql integer FOR-loops, andabout 19 years ago
Started threadpgsql: Note incompatibility with Oracle's version of FOR ...about 19 years ago
Replied (own)plpgsql FOR loop doesn't guard against strange step valuesabout 19 years ago