X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E5207D1B33D for ; Fri, 23 Jul 2004 17:59:03 -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 23852-10 for ; Fri, 23 Jul 2004 20:59:01 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9AEFCD1B181 for ; Fri, 23 Jul 2004 17:58:58 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i6NKwtZb028011; Fri, 23 Jul 2004 16:58:56 -0400 (EDT) To: David Fetter Cc: Peter Eisentraut , Robert Treat , Joe Conway , elein , pgsql-docs@postgresql.org Subject: Re: [HACKERS] Tutorial In-reply-to: <20040723204036.GY7751@fetter.org> References: <20040722222104.GU7751@fetter.org> <200407222240.45890.xzilla@users.sourceforge.net> <15070.1090552467@sss.pgh.pa.us> <200407230903.30389.peter_e@gmx.net> <20040723185146.GV7751@fetter.org> <27387.1090611107@sss.pgh.pa.us> <20040723193413.GW7751@fetter.org> <27773.1090614640@sss.pgh.pa.us> <20040723204036.GY7751@fetter.org> Comments: In-reply-to David Fetter message dated "Fri, 23 Jul 2004 13:40:36 -0700" Date: Fri, 23 Jul 2004 16:58:55 -0400 Message-ID: <28010.1090616335@sss.pgh.pa.us> From: Tom Lane 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: 200407/29 X-Sequence-Number: 2437 David Fetter writes: > On Fri, Jul 23, 2004 at 04:30:40PM -0400, Tom Lane wrote: >> If we're going to remove from the tutorial every feature for which >> any aspect is deemed by someone to be broken, the tutorial is liable >> to become quite short. > Are there other pieces that are broken? Between the locale behavior and the trailing-spaces behavior, one could make the case that the entire set of textual datatypes are broken. Other examples will occur to your thought if you follow pgsql-bugs. My point here is that one man's unusably broken feature may be another man's quite useful feature. Postgres is a work in progress, and probably always will be. I don't object to pointing out shortcomings, but removing all mention of a feature because it has some shortcomings seems not the best way. regards, tom lane