X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6821214B2821; Wed, 11 Aug 2004 23:04:01 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 57253-04; Thu, 12 Aug 2004 02:04:00 +0000 (GMT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id A1D7614B2868; Wed, 11 Aug 2004 23:03:59 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 835533B04C; Wed, 11 Aug 2004 23:04:05 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 68C143B017; Wed, 11 Aug 2004 23:04:05 -0300 (ADT) Date: Wed, 11 Aug 2004 23:04:05 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: "Gavin M. Roy" Cc: "Marc G. Fournier" , Josh Berkus , Dave Page , PostgreSQL www Subject: Re: PGSQL-WINDOWS mailing list? In-Reply-To: <411ACEF2.8060607@ehpg.net> Message-ID: <20040811230342.S62519@ganymede.hub.org> References: <200408110930.22269.josh@agliodbs.com> <20040811224915.O62519@ganymede.hub.org> <411ACEF2.8060607@ehpg.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/91 X-Sequence-Number: 4866 On Wed, 11 Aug 2004, Gavin M. Roy wrote: > Don't ya think pgsql-sql-windows is a bit overkill? It's not like pg's > behavior re sql changes on windows. hey, I'm just throwing out suggestions :) and .. agreed, that one would be overkill ... > > Gavin > > Marc G. Fournier wrote: > >> On Wed, 11 Aug 2004, Josh Berkus wrote: >> >>> Dave, >>> >>>> That's a different issue altogether though (perfectly valid though). >>>> Is >>>> there a more appropriate way to split the existing groups perhaps? I'm >>>> opposed to shifting the windows users onto a platform specific group >>>> just because there's a lot of them. I'm not opposed to shifting them >>>> if >>>> we find there are lots of platform specific problems though. >>> >>> >>> Well, unfortunately, at least 70% of the Windows users can be counted on >>> not >>> to differentiate platform-specific issues from general ones. And given >>> the >>> flakyness of the platform, I expect there to be continuous issues. >>> Also, I'd >>> really rather not have a 25-post thread on PGSQL-SQL discussing how >>> XP-SP3 >>> breaks PostgreSQL. >>> >>> While there are other possible lists we could add, the advantage of >>> PGSQL-WINDOWS is that it would attract a substantial portion of the new >>> users, which, for example, a list named PGSQL-INSTALL might not. >> >> >> I'm not ant-pgsql-windows, but I fear that the one thing you are trying to >> avoid is going to happen if we do create it ... namely, all new windows >> users will subscribe to that one list and post everything under the sun to >> it, making that one list pretty useless :( >> >> If anything, altho it might be long, let's do something like: >> >> pgsql-general-windows >> pgsql-novice-windows >> pgsql-admin-windows >> pgsql-sql-windows >> >> or something like that ... so that its not just the one list ... >> >> ---- >> Marc G. Fournier Hub.Org Networking Services >> (http://www.hub.org) >> Email: scrappy@hub.org Yahoo!: yscrappy ICQ: >> 7615664 >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 9: the planner will ignore your desire to choose an index scan if your >> joining column's datatypes do not match > > > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664