| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] Trivial patch to double vacuum speed |
| Date: | 2006-09-04 23:51:31 |
| Message-ID: | 44FCBC03.2000507@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> I don't have a concrete proposal to make, but I do think that the
> current patch-queue process is not suited to the project as it stands
> today. Maybe if this issue-tracking stuff gets off the ground, we
> could let developers place ACK or NAK flags on patches they've looked
> at, and have some rule about ACK-vs-NAK requirements for something to go
> in.
How about *requiring* test cases that prove the patch?
Sincerely,
Joshua D. Drake
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-09-04 23:52:10 | Re: [PATCHES] Trivial patch to double vacuum speed |
| Previous Message | Greg Sabino Mullane | 2006-09-04 23:49:58 | Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s` |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-09-04 23:52:10 | Re: [PATCHES] Trivial patch to double vacuum speed |
| Previous Message | Tom Lane | 2006-09-04 23:40:54 | Re: [PATCHES] Trivial patch to double vacuum speed |