From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org>, "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
Subject: | Re: List traffic |
Date: | 2010-05-14 14:21:02 |
Message-ID: | 4BED15FE0200002500031728@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-chat pgsql-general pgsql-hackers |
"Greg Sabino Mullane" <greg(at)turnstep(dot)com> wrote:
> Would anyone argue against rolling those two (sql and admin) into
> -general as a first step?
At the risk of repeating myself, I won't be able to keep up with the
traffic of the combined list; so rather than read 100% of the
messages from a smaller set, I'll need to pick and choose based on
subject line or some such. I get the impression that other people,
who read different subsets of the lists, will be forced to a similar
change. That may result in either some posts "slipping through the
cracks" or in increasing the burden of responding to the posts for
those brave few who wade through them all.
Personally, I'm not convince that merging current lists will solve
more problems than it will create.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-05-14 14:26:15 | Re: List traffic |
Previous Message | Narasimha Murthy-VRFX87 | 2010-05-14 14:20:02 | Re: Clarification required: autovacuum and VACUUM command mode |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-05-14 14:26:15 | Re: List traffic |
Previous Message | Greg Sabino Mullane | 2010-05-14 14:10:32 | Re: List traffic |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-05-14 14:26:15 | Re: List traffic |
Previous Message | Greg Sabino Mullane | 2010-05-14 14:10:32 | Re: List traffic |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-05-14 14:26:15 | Re: List traffic |
Previous Message | Florian Pflug | 2010-05-14 14:20:22 | Re: Row-level Locks & SERIALIZABLE transactions, postgres vs. Oracle |