Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCHES] Trivial patch to double vacuum speed - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: [PATCHES] Trivial patch to double vacuum speed
Date
Msg-id 44FCBC03.2000507@commandprompt.com
Whole thread Raw
In response to Re: [PATCHES] Trivial patch to double vacuum speed  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] Trivial patch to double vacuum speed  (Bruce Momjian <bruce@momjian.us>)
Re: [PATCHES] Trivial patch to double vacuum speed  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [PATCHES] Trivial patch to double vacuum speed  (Gavin Sherry <swm@linuxworld.com.au>)
Re: [PATCHES] Trivial patch to double vacuum speed  (Hannu Krosing <hannu@skype.net>)
List pgsql-hackers
Tree view 
> 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
solutionssince 1997             http://www.commandprompt.com/

pgsql-hackers by date:

Previous
From: "Greg Sabino Mullane"
Date:
Subject: Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s`
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] Trivial patch to double vacuum speed