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

From: Steve Atkins <steve(at)blighty(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql-patches reply-to (was Re: [PATCHES] selecting
Date: 2006-08-17 16:40:29
Message-ID: AF782F08-3A89-4390-A598-37529B370362@blighty.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


On Aug 17, 2006, at 9:30 AM, Magnus Hagander wrote:

>>>>> Ever since pgsql-patches replies started going to -hackers,
>>>>> threading doesn't work anymore, so I for one can't tell what this
>>>>> refers to at all.
>>>>
>>>> Yeah, that experiment hasn't seemed to work all that well for me
>>>> either. Do you have another idea to try, or do you just want to
>>>> revert to the old way?
>>>
>>> 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).

Cheers,
Steve

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthew T. O'Connor 2006-08-17 16:41:57 Re: Autovacuum on by default?
Previous Message Josh Berkus 2006-08-17 16:40:14 Re: Autovacuum on by default?

Browse pgsql-patches by date

  From Date Subject
Next Message Chris Mair 2006-08-17 16:50:42 Re: [HACKERS] selecting large result sets in psql using
Previous Message Joe Conway 2006-08-17 16:37:19 Re: pgsql-patches reply-to (was Re: [PATCHES] selecting