Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bDlFA-0001oc-OD for pgsql-performance@arkaria.postgresql.org; Fri, 17 Jun 2016 04:18:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bDlFA-00071H-BI for pgsql-performance@arkaria.postgresql.org; Fri, 17 Jun 2016 04:18:56 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bDlF9-000716-PG for pgsql-performance@postgresql.org; Fri, 17 Jun 2016 04:18:55 +0000 Received: from mail-oi0-x230.google.com ([2607:f8b0:4003:c06::230]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bDlF7-0004AP-6o for pgsql-performance@postgresql.org; Fri, 17 Jun 2016 04:18:54 +0000 Received: by mail-oi0-x230.google.com with SMTP id p204so100659454oih.3 for ; Thu, 16 Jun 2016 21:18:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1aTNgO/FORpGS+gtIltUaCFhZzvOGQBKi0Nx8bhLknc=; b=JH+pu8qGLpyDsVEGrSlnriw8A5mW6lzV5Ani4jknvm2LMfhV4AmQIRUbefHPvGlBcv 9Mzucj9tO+nfvfAnCIrGpcWNAhDEcsz2gxQnWiuo6guxFBCA6rqlNKxDBt9bxXQFvDOf HR+xGfoeF++Y+HH6uC5TDJI6kT+s0wqhUfqHY9Vt0+XxwLkzh6IaPB+06cUt6sDWCAPq U+WnweJFSR9JL1NuLKdN3UpDkAnqQ1+z6ANrYfczXuJo95b+RJK71fc5kwf1P54q5qGy V13WZdO4/7jV1G24YUPECtWE99KwpcrL2owFGGGw/yk4AjtwKOXvr12YxZVUvjRhpWAT FMMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1aTNgO/FORpGS+gtIltUaCFhZzvOGQBKi0Nx8bhLknc=; b=c2Brhxr4mIC/1EJSknaivJFBM0sBaIRvOApIFVp2mrsOy0Zq+/ix9px7PyX1wqv+8L Hb7c3MMkebfRiDrZJCiip2Tou3gk9BB/W1FSqhXnhVTKr0RGujmLlm1H2vX0nRjYc9Hj ktzKrFgy06LGsne5dqmfAzkAwDY2wdLNL0wL1QQ6PtcfBxIsDmfH5Gnd1yTeV/mSKLmY rac54sz7HbnKgzrtc4imh2ytfI7WRwLH33HJdqda392HbumLKRv9ioT2/KF6MHajkjqj xXsZ4pja63AhBsypopRBYWxD7dP29K4XbG/34F4Pbx0hDi44yL0g0g6Lf2OxbgdNP9rW oKCg== X-Gm-Message-State: ALyK8tILhu0LDjBxsg1+bQQ6xGf9QRc7DU6TAm45nuQvJzSI3SR0Vn+sGQJK2ajuJpSuttXjxq2Nz+Y3OywusA== X-Received: by 10.157.9.199 with SMTP id 7mr312327otz.52.1466137132651; Thu, 16 Jun 2016 21:18:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.72.133 with HTTP; Thu, 16 Jun 2016 21:18:52 -0700 (PDT) In-Reply-To: References: From: Claudio Freire Date: Fri, 17 Jun 2016 01:18:52 -0300 Message-ID: Subject: Re: Indexes for hashes To: julyanto@equnix.co.id Cc: Ivan Voras , postgres performance list Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On Fri, Jun 17, 2016 at 1:09 AM, julyanto SUTANDANG wrote: > This way is doing faster using crc32(data) than hashtext since crc32 is > hardware accelerated in intel (and others perhaps) > this way (crc32) is no way the same as hash, much way faster than others... > > Regards, Sure, but I've had uniformity issues with crc32. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance