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 1oD0yy-0002XG-Jt for pgsql-hackers@arkaria.postgresql.org; Sun, 17 Jul 2022 09:54:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oD0yw-0002C8-Ge for pgsql-hackers@arkaria.postgresql.org; Sun, 17 Jul 2022 09:54:34 +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 1oD0yw-0002Bz-72 for pgsql-hackers@lists.postgresql.org; Sun, 17 Jul 2022 09:54:34 +0000 Received: from mout-b-105.mailbox.org ([2001:67c:2050:102:465::105]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oD0ys-0005kA-9x for pgsql-hackers@lists.postgresql.org; Sun, 17 Jul 2022 09:54:33 +0000 Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:b231:465::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-105.mailbox.org (Postfix) with ESMTPS id 4Lm0my0Ny9z9sj7; Sun, 17 Jul 2022 11:54:26 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aboutsource.net; s=MBO0001; t=1658051666; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JrEDSK6ustBynhsKVg8Gqf+7Cldjs7QOnZoymjW+Toc=; b=dfd64y5SG1l1FVYjry1B42bP01JhAY/anVdLYjPYRxSY4N5APX52dsFFhzgwoYlynKBqlO /Wwew0vRaMMGoQ1lkWt5zlMrKr5wLTs530WV/5VMDMgYL4A9HAKvyqThWwniJQynAvIj38 cNISqm6R1ZO5l1qxWGh4F2xaeKPHa/g34j1lmjn8/GQWY7uUsKc3dKLMQJUlqbGalvK2Y7 KmyNxcUSJmkDvY1DI434ls4dI/uPT59V7wtqm6T46XlmwTlR0AGuZ7cneLYxHRrEbjzLBP fPjsm3+4uM8fDnhR4jGmQYfFl2p8Hv2YT3Z+9f+I2mmxcMRb2iHyGoUxAnt3PA== Message-ID: Date: Sun, 17 Jul 2022 11:54:22 +0200 MIME-Version: 1.0 Subject: Re: Proposal to introduce a shuffle function to intarray extension Content-Language: de-DE To: "David G. Johnston" Cc: Thomas Munro , PostgreSQL Hackers References: <9d160a44-7675-51e8-60cf-6d64b76db831@aboutsource.net> From: Martin Kalcher In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Lm0my0Ny9z9sj7 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Am 17.07.22 um 05:32 schrieb David G. Johnston: > > +SELECT sample('{1,2,3,4,5,6,7,8,9,10,11,12}', 6) != > sample('{1,2,3,4,5,6,7,8,9,10,11,12}', 6); > + ?column? > +---------- > + t > +(1 row) > + > > While small, there is a non-zero chance for both samples to be equal. This > test should probably just go, I don't see what it tests that isn't covered > by other tests or even trivial usage. > Hey David, you are right. There is a small chance for this test to fail. I wanted to test, that two invocations produce different results (after all the main feature of the function). But it can probably go. Martin