Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCWKK-0002Fd-9d for pgsql-general@arkaria.postgresql.org; Tue, 03 Jan 2023 01:42:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pCWJL-0004Tk-39 for pgsql-general@arkaria.postgresql.org; Tue, 03 Jan 2023 01:41:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCWJK-0004TZ-NC for pgsql-general@lists.postgresql.org; Tue, 03 Jan 2023 01:41:50 +0000 Received: from mail-pg1-x535.google.com ([2607:f8b0:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pCWJI-0005LJ-B6 for pgsql-general@lists.postgresql.org; Tue, 03 Jan 2023 01:41:50 +0000 Received: by mail-pg1-x535.google.com with SMTP id d10so19191944pgm.13 for ; Mon, 02 Jan 2023 17:41:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=zZhoJ2040s1hFrm+Qk3wWDiiNTdsKf77equJidI8cDg=; b=Cm2D1XLQNNcxS2wsK8bVvXHjccmgk22mDLjxBwdRoIpXd8hKyUF2g/ct21DRnEahQ3 6/MxJUxep8Yv7uj0ICvF1SUrKgRXdKrd3Sc0AGkx95Iy1XOg0wlHO/Zw9Oakholm/gV1 vcNgWq74Wn3oD9jdAye1JgVx44W4J0vTUZ+P7DKtIGY5GIZU2JbF1v3UItqxgdoW8Y19 qn6WNmKXsTcICm29QU0UJcsxIjmmzvz8ExMO3vzlc+WKMrAyc9nKKyB9tHdR6xTWzILo gW/Cj87h8r7+2j40Zbqd3EFbJfnxoE9eS33DNJ2AyDPKcLBN0Levj5++bQZWfl/i69p1 CUcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=zZhoJ2040s1hFrm+Qk3wWDiiNTdsKf77equJidI8cDg=; b=TRonD+1ZRTHlwSxcOb9N+A/wOBn4bg9ro9b96FK+x7LyoNBHDuy9qbAZusnH0/j0tO GSOEr/FXGS5XKv+kpDrdEPid4FYVL5kaCSaHzBr9S7UkQ3HQX1qu97k3fpL5ewvPvE0P oeZZ6Lnks8oenhdDo+76miJh9L+8ZBFY/Xsb0B0pBxs2ldm48P+8P4zzsnhHoIXQTgJK lxF02qGGxNtwyJsQlUUSEVzP35gYk5QjSnsCqlDmdicuXTkvdjVOdWJEswzjqUrtbj++ C3Y1oUyrcuhpr+qu1CnZLQFxE+adRnaXfv4YtcWOe6qx26qEL7VL5qV+DcB7c0ex0iNp Mfeg== X-Gm-Message-State: AFqh2kpHXKKxgAKhK4/o8RmzBw1uuHieDJ7pYb0sLpZnqaPBangBMdtq OX+t6ih9pozAxJSILbNzOgA= X-Google-Smtp-Source: AMrXdXusDpHniZyztIKeKYV0aqXEOwJHnrpFrKUYiQbIQ6LISr4iHrBbVNih7K/XEiwJEhpYexpdfQ== X-Received: by 2002:aa7:9f4b:0:b0:582:6732:ee03 with SMTP id h11-20020aa79f4b000000b005826732ee03mr5898089pfr.9.1672710105845; Mon, 02 Jan 2023 17:41:45 -0800 (PST) Received: from jrouhaud (118-160-13-56.dynamic-ip.hinet.net. [118.160.13.56]) by smtp.gmail.com with ESMTPSA id a184-20020a624dc1000000b00576cc60e5c9sm19125999pfb.87.2023.01.02.17.41.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Jan 2023 17:41:44 -0800 (PST) Date: Tue, 3 Jan 2023 09:41:41 +0800 From: Julien Rouhaud To: "jacktby@gmail.com" Cc: pgsql-general Subject: Re: what kind of hash algorithm is used by hash_bytes()? Message-ID: <20230103014141.jwxrmzt47fbwevm7@jrouhaud> References: <202301030030258980553@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202301030030258980553@gmail.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Tue, Jan 03, 2023 at 12:30:27AM +0800, jacktby@gmail.com wrote: > jacktby@gmail.com > -------------- > I can't understand the hash_bytes() func in src/backend/access/hash/hashfunc.c, it's published by a paper or others? > Can you give me some materials to study it in depth? It's documented at the beginning of hashfn.c.