X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id D603D9DC86B for ; Thu, 16 Feb 2006 20:18:09 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 66723-09 for ; Thu, 16 Feb 2006 20:18:12 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by postgresql.org (Postfix) with ESMTP id 66D579DC83D for ; Thu, 16 Feb 2006 20:18:07 -0400 (AST) Received: from [84.157.0.176] (helo=lunix.schabi.de) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis), id 0MKwtQ-1F9tK40U5m-0000cW; Fri, 17 Feb 2006 01:18:10 +0100 Received: from [127.0.0.1] (localhost [127.0.0.1]) by lunix.schabi.de (Postfix) with ESMTP id 448171CD32E; Fri, 17 Feb 2006 01:18:06 +0100 (CET) Message-ID: <43F5163E.2020108@logix-tt.com> Date: Fri, 17 Feb 2006 01:18:06 +0100 From: Markus Schaber User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: PFC CC: pgsql-performance@postgresql.org Subject: Re: [HACKERS] qsort again (was Re: Strange Create Index References: <43F38867.6010701@gpdnet.co.uk> <19510.1140036968@sss.pgh.pa.us> <19779.1140038874@sss.pgh.pa.us> <43F39E53.1020009@gpdnet.co.uk> <20781.1140046109@sss.pgh.pa.us> <7.0.1.0.2.20060215194635.03b55da0@earthlink.net> <21615.1140052893@sss.pgh.pa.us> <7.0.1.0.2.20060215223710.03a7c618@earthlink.net> <20060216113522.GA3461@uio.no> <7.0.1.0.2.20060216071053.0385a1a8@earthlink.net> <43F481CD.2010509@logix-tt.com> <43F4A7D8.4050907@modgraph-usa.com> <29277.1140110108@sss.pgh.pa.us> <1140128256.9076.254.camel@archimedes> In-Reply-To: X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:a9554655f07a4e401310f2acfb43f5bf X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.126 required=5 tests=[AWL=0.126] X-Spam-Score: 0.126 X-Spam-Level: X-Archive-Number: 200602/269 X-Sequence-Number: 17255 Hi, PFC, PFC schrieb: > By the way, I'd like to declare my zipcode columns as SQL_ASCII > while the rest of my database is in UNICODE, so they are faster to > index and sort. Come on, MySQL does it... Another use case for parametric column definitions - charset definitions - and the first one that cannot be emulated via constraints. Other use cases I remember were range definitions for numbers or PostGIS dimension, subtype and SRID, but those cann all be emulated via checks / constraints. Markus