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 C2BCE14B2884; Wed, 11 Aug 2004 22:59:41 -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 84770-05; Thu, 12 Aug 2004 01:59:37 +0000 (GMT) Received: from tetra.ehpg.net (tetra.ehpg.net [216.218.206.34]) by svr1.postgresql.org (Postfix) with ESMTP id 6733B14B2883; Wed, 11 Aug 2004 22:59:35 -0300 (ADT) Received: from adsl-67-122-138-50.dsl.pltn13.pacbell.net ([172.16.1.35]) [67.122.138.50]by tetra.ehpg.netwith asmtp(Exim 4.34 #1 (Gentoo Linux 1.4))id 1Bv4sU-0005Ur-55; Wed, 11 Aug 2004 18:59:38 -0700 Message-ID: <411ACEF2.8060607@ehpg.net> Date: Wed, 11 Aug 2004 18:59:14 -0700 From: "Gavin M. Roy" User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Marc G. Fournier" Cc: Josh Berkus , Dave Page , PostgreSQL www Subject: Re: PGSQL-WINDOWS mailing list? References: <200408110930.22269.josh@agliodbs.com> <20040811224915.O62519@ganymede.hub.org> In-Reply-To: <20040811224915.O62519@ganymede.hub.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanned: Clean 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/90 X-Sequence-Number: 4865 Don't ya think pgsql-sql-windows is a bit overkill? It's not like pg's behavior re sql changes on windows. 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