Re: pgsql-patches reply-to (was Re: [PATCHES] selecting

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Steve Atkins" <steve(at)blighty(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql-patches reply-to (was Re: [PATCHES] selecting
Date: 2006-08-17 16:56:09
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA0FB3D@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> >>> I'd vote for reverting to the old way. Anyone serious
> about hacking
> >>> should be on both lists.
> >
> > Then why bother with two different lists?
> >
> > If developers need to be on both list (which I beleive they
> do), and
> > the focus of both lists is developers, then why not just
> remove one of
> > them and get rid of the problem?
>
> One reason might be that a lot of application developers who
> develop applications or modules associated with PG, but not
> the core PG code itself also lurk on -hackers, as it's by far
> the best way to keep up with the status of various PG
> enhancements (and also an excellent place to pick up a lot of
> undocumented good practices).

Won't you learn even more good practices if you actually see the patches
as well? :-P

The bottom line is, I think, does the volume of mail on -patches
actually make a big difference given the much higher volume on -hackers?
(If you just want to skip the patches, just set up attachment filtering
on the list..)

//Magnus

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-08-17 16:56:15 Improvement for logging bind parameters
Previous Message Matthew T. O'Connor 2006-08-17 16:55:48 Re: Autovacuum on by default?

Browse pgsql-patches by date

  From Date Subject
Next Message Gregory Stark 2006-08-17 16:59:11 Re: pgsql-patches reply-to (was Re: [PATCHES] selecting
Previous Message Chris Mair 2006-08-17 16:54:28 Re: [HACKERS] selecting large result sets in psql using