Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f2XJp-0001NU-34 for pgsql-committers@arkaria.postgresql.org; Sun, 01 Apr 2018 07:22:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f2XJm-00072B-JT for pgsql-committers@arkaria.postgresql.org; Sun, 01 Apr 2018 07:22:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f2XJk-000721-W2 for pgsql-committers@lists.postgresql.org; Sun, 01 Apr 2018 07:22:22 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f2XJg-00036v-5j for pgsql-committers@lists.postgresql.org; Sun, 01 Apr 2018 07:22:20 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id D8E9A20CE2; Sun, 1 Apr 2018 03:22:13 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 01 Apr 2018 03:22:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=s5Gsxo/Pve0ckY7NcBJJKtNKHLD6pA2Gi7lovUHsDfc=; b=wYW5Fg1D vtDTNeSTudGCB6ikH3v+D6wyG9oMI0mNIoiikzICV3ScVaCzzE7k3Lmi+3WCHngJ cVVxU0Yth1OeJU5QQzM82D8me+mDdhAcN0zbxOoy/N3tZKayZ4JZIRTGXpNwkS3Y okt5kHBcjyNJT4WckUCd46f4porb1DgzwqRIgLNr4WsYFqBQ6OoDOjrcjq0XDnFx 2EHrhXhXIrfV+y9pjU3KoNx1W/52Z6TT4xkqj9CWFsAhW9kw/KZnZYV8GTZYP0yt 5dZNZHqfJs5y8bGrH9VRGcSJ3ZYmOm1o//6lA2XXLoJkRTMSE5645BtaDaVhUKCa fW71jahLMCX/Cw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=s5Gsxo/Pve0ckY7NcBJJKtNKHLD6p A2Gi7lovUHsDfc=; b=N60+X3TB4JngAOHVilPwoL4BAoiDX89u04cvc2E0mOYiG INCa7JkiMKyPNiiMEbgkZ89Ol+WwJyqwsZuksfqy3qEzLdswsQPOx5YTluERGSEf fa7+HEP2MeTDqMLHmQEpd3XX5BvAr/zlTl22vaLfs+Vilq0p+j8rh9sTfn7y3BHO fyMypd5gN6zYYtAhK90tO9Mz6c3o+fuxBU+Y2Jx1kLTXUULmACaA3SUSkCs2IetN szgZL/1UJu/7FrhqdFe2B13A9xLAqYJ23sFuyjlbDqfII9hBpVQl1L/k+U/yymGd F1/b2EEeN12Z27q2VQ/vggZ2u53Tp5VUdD3sYMG3w== X-ME-Sender: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id D41CC10252; Sun, 1 Apr 2018 03:22:11 -0400 (EDT) Date: Sun, 1 Apr 2018 16:22:08 +0900 From: Michael Paquier To: Fabien COELHO Cc: Tom Lane , Teodor Sigaev , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Set random seed for pgbench. Message-ID: <20180401072208.GB2211@paquier.xyz> References: <32390.1522464534@sss.pgh.pa.us> <10686.1522514072@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="U+BazGySraz5kW0T" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --U+BazGySraz5kW0T Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Mar 31, 2018 at 07:43:38PM +0200, Fabien COELHO wrote: > Indeed, I clearly misunderstood its usage pattern. I looked at its source > ("src/port/pg_strong_random.c") where the function is always defined and is > documented as returning false if it does not find a strong random source, so > I though that checking for this was enough. But indeed its > compilation fails if no source is provided. I have not check in details this thread so I may be saying something stupid... But if you are looking for a frontend implementation for strong randoms, please extract pg_frontend_random in fe-auth-scram.c and move it to its own file for example in src/common as a frontend-only file. When working on SCRAM, I recall mentioning that but Heikki has kept the code in its current shape for simplicity. As far as I can see, there is no reason to issue an error in set_random_seed() either in pgbench code. -- Michael --U+BazGySraz5kW0T Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlrAiKAACgkQnvQgOdby QH3PIw/9E2R0ngw0zYEURbdd2KzZIsuLzU9hx95hLxLZoFdfCwvTaFvoDaTovjrZ XJkkXnS1aAyAv8RDdUc+khY6vg4JmVGCNur1QCPSYdzbCP6geG42iT5Ezy4rSYyS dr52V46swmdy0XsOj+8y0DSVTWx27Ti3L5Ou9f9tOUpTzu2z/V2c7RKe2bd+7GNz qafM5VQIJ7c3hDOK6oQxfzW5l0zufBTCKlgTw7TT8PVFnRFtXuc5QgGGJtzBgUSB J2kGtQHLUT5xcDQ9pZCD3darTq93mWT6y0DQ4ZStcXDSy8KIYh26x6c4hFadocT+ 6IuABVVT+PmlFPFLr/T0hW1DerhaH2bDw7emheeZG3gOQevlkZkhJgIUR/UWdQHK Crxbc58+t9irZHRYhjGb2NfpE5Xz2KaSBTVgKpe5JMOgo1ScM6Qrj4c/vLXJbeIE VKqYnkWiUT1C65OpYPaOjJCJcmyAvm5laXp/+5a8IchdcAb3JySaDycPwclPpH+G KxJv2KE41W7fVVj9F5xHijmMvPFthAOPCEnbeF10CpI/N2mklRa8C/jYjJXfPKWf SFd+E9Ty+zYwheJg8b5I+iOXtWFaprShK8rN/kfryyWcm14qoWQ6t+jj1b3WVl/6 vsDjmo7Hu+ok7U/WRKsfcfQSUb5MQ9az67py96VvAh1Rjcuhuu4= =QhPx -----END PGP SIGNATURE----- --U+BazGySraz5kW0T--