| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sean Chittenden <sean(at)chittenden(dot)org> |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Kevin Brown <kevin(at)sysexperts(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Heads up: 7.3.3 this Wednesday |
| Date: | 2003-05-16 21:51:54 |
| Message-ID: | 284.1053121914@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Sean Chittenden <sean(at)chittenden(dot)org> writes:
>> BTW, if anyone is looking for that patch, it was at
>> http://archives.postgresql.org/pgsql-hackers/2003-04/msg00260.php
> Are there any test cases to get this bug to fire? I haven't had any
> problems with this particular bug so I can apply this patch, but I
> can't promise that my use of the patch will result in anything useful
> other than, "nothing's broke yet" since I haven't had any real
> problems with 7.3.2 other than the deferred trigger speed.
"Nothing's broke yet" would be a useful report. I just would like to
see some more mileage on the beast before we let it loose on the
unsuspecting world. Test cases aren't really the point --- we know what
we expect them to do. It's the cases we didn't think of that worry me
at times like this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-05-16 21:57:20 | Re: Heads up: 7.3.3 this Wednesday |
| Previous Message | Tom Lane | 2003-05-16 21:45:22 | Re: Error message style guide, take 2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-05-16 21:57:20 | Re: Heads up: 7.3.3 this Wednesday |
| Previous Message | Sean Chittenden | 2003-05-16 21:44:53 | Re: Heads up: 7.3.3 this Wednesday |