From: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: List traffic |
Date: | 2010-05-13 18:05:38 |
Message-ID: | alpine.BSF.2.00.1005131503030.22297@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-chat pgsql-general pgsql-hackers |
My thought had been a split along the lines of major components of the
server ... for instance, a totally seperate list for HS related issues, so
that, if nothing else, those 'lurkers' that are only interested in
developments on that front could be there but not on the main stream
-hackers ... almost like seperate working groups ...
Twas just a thought ...
On Wed, 12 May 2010, Greg Stark wrote:
> On Wed, May 12, 2010 at 5:24 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> The difference between discussing a patch and discussing an idea that
>> might lead to a patch is fairly fine.
>
> And importantly -- who would be able to subscribe to one and not the
> other? If you have to subscribe to both to get make any sense of
> things then there's no point.
>
> Fwiw I'm having trouble keeping up these days too. And I'm quite
> accustomed to very heavy traffic email. I've been throwing all
> postgres related lists into one folder and skimmed through it looking
> for important threads. However this has now broken down. There are
> about 45 new threads every day. I've been travelling for a bit and am
> now 1,500 threads behind...
>
> If we can find a way to split the content sensibly so I could stop
> reading some of it that would be helpful. But cutting splitting it
> along subject matter where both sets of subject matter need to be seen
> by the same people doesn't really help.
>
> I'm thinking I'll move -general (and the useless -novice) to another
> folder. But I'm left wondering what to do with -admin and
> -performance. They're a random mix of user content and developer
> content. I'll probably move them along with -general but that means I
> won't be likely to see any development discussion on them in the
> future.
>
>
>
>
> --
> greg
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy(at)hub(dot)org http://www.hub.org
Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(at)hub(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Yeb Havinga | 2010-05-13 19:06:53 | Re: List traffic |
Previous Message | Ray Stell | 2010-05-13 16:04:23 | Re: upgrade proc with pitr standby |
From | Date | Subject | |
---|---|---|---|
Next Message | Yeb Havinga | 2010-05-13 19:06:53 | Re: List traffic |
Previous Message | Magnus Hagander | 2010-05-13 13:44:29 | Re: List traffic |
From | Date | Subject | |
---|---|---|---|
Next Message | S G | 2010-05-13 18:24:21 | Re: SQL code runs slower as a stored function |
Previous Message | S G | 2010-05-13 17:39:21 | Re: SQL code runs slower as a stored function |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2010-05-13 18:25:34 | Re: pg_upgrade code questions |
Previous Message | Andrew Dunstan | 2010-05-13 17:32:48 | Re: pg_upgrade code questions |