Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cS8tF-00049g-QT for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Jan 2017 20:56:01 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cS8tF-00012e-DG for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Jan 2017 20:56:01 +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.84_2) (envelope-from ) id 1cS8rq-0007AB-5C for pgsql-hackers@postgresql.org; Fri, 13 Jan 2017 20:54:34 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cS8rn-0007Vv-4w for pgsql-hackers@postgresql.org; Fri, 13 Jan 2017 20:54:33 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v0DKsOYr021885; Fri, 13 Jan 2017 15:54:24 -0500 From: Tom Lane To: Florian Weimer cc: Haribabu Kommi , PostgreSQL-development Subject: Re: gettimeofday is at the end of its usefulness? In-reply-to: <87wpdy1ya4.fsf@mid.deneb.enyo.de> References: <31856.1400021891@sss.pgh.pa.us> <20140515185614.GG25053@momjian.us> <20237.1465397783@sss.pgh.pa.us> <15740.1482788055@sss.pgh.pa.us> <87y3yyfqqe.fsf@mid.deneb.enyo.de> <4130.1483045351@sss.pgh.pa.us> <87wpdy1ya4.fsf@mid.deneb.enyo.de> Comments: In-reply-to Florian Weimer message dated "Fri, 13 Jan 2017 21:48:51 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <21883.1484340864.1@sss.pgh.pa.us> Date: Fri, 13 Jan 2017 15:54:24 -0500 Message-ID: <21884.1484340864@sss.pgh.pa.us> X-Pg-Spam-Score: -5.1 (-----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Florian Weimer writes: > glibc has some test cases which fail because clock_gettime gives > inconsistent results. This has been fixed in current kernels, but I > don't know if everyone uses them. hmm, for which clock IDs? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers