From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | darcy(at)druid(dot)net (D'ArcyJ(dot)M(dot)Cain), pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Syntax errors in current tree |
Date: | 1999-01-18 16:07:14 |
Message-ID: | 355.916675634@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> Not really a problem. Most patch problems are either my mucking with it
> to merge it with other changes, or platform-specific problems that the
> tester would never have see. For example, Win32 used EINTR without
> including errno.h.
And, by the same token, whoever does commit a patch might fail to notice
a platform-specific problem that didn't happen to show up on his
platform. You can't really expect things to be 100% tested before they
hit the CVS tree (that's why we have a release cycle).
My experience so far is that the Postgres CVS sources are pretty stable;
most of the time they work, which can't be said for some other projects
I'm involved in :-(. Not that we shouldn't strive to do even better,
but an occasional breakage is going to happen.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-01-18 16:36:48 | Re: [HACKERS] Syntax errors in current tree |
Previous Message | Michael Meskes | 1999-01-18 15:56:17 | performance test |