From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
Cc: | darcy(at)druid(dot)net, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Syntax errors in current tree |
Date: | 1999-01-18 16:36:48 |
Message-ID: | 199901181636.LAA11600@candle.pha.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.
Problem is that I rarely have a solid block of time to apply the
patches. (I used to.) It is done in pieces as I can get time during
the day. This makes for mistakes.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-01-18 16:37:12 | Re: [HACKERS] Postgres Speed or lack thereof |
Previous Message | Tom Lane | 1999-01-18 16:07:14 | Re: [HACKERS] Syntax errors in current tree |