X-Original-To: pgsql-bugs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A312532A611 for ; Fri, 15 Oct 2004 02:26:11 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 25288-06 for ; Fri, 15 Oct 2004 01:26:05 +0000 (GMT) Received: from dic-mail.telstra.net (crash.telstra.net [203.50.0.185]) by svr1.postgresql.org (Postfix) with ESMTP id 4DE4E32A518 for ; Fri, 15 Oct 2004 02:26:07 +0100 (BST) Received: from telstra.net (xena.telstra.net [203.50.0.233]) by dic-mail.telstra.net (8.12.11/8.12.11) with ESMTP id i9F1Q56r010369 for ; Fri, 15 Oct 2004 11:26:06 +1000 Message-ID: <416F2647.9040103@telstra.net> Date: Fri, 15 Oct 2004 11:22:15 +1000 From: Justin Clift User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20040406 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-bugs@postgresql.org Subject: [Fwd: Re: misc/72498: Libc timestamp code on jailed SMP machine generates incorrect results] References: <17cf921877c71d81bab3ca376f9add6067033546@postgresql.org> In-Reply-To: <17cf921877c71d81bab3ca376f9add6067033546@postgresql.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/172 X-Sequence-Number: 9635 Hi all, Does anyone have further input on this? Regards and best wishes, Justin Clift Justin Clift wrote: > ------------------------------------------------------------------------ > > Subject: > [Fwd: Re: misc/72498: Libc timestamp code on jailed SMP machine > generates incorrect results] > From: > Justin Clift > Date: > Tue, 12 Oct 2004 10:47:30 +1000 > To: > pgsql-bugs@postgresql.org > > > Hi guys, > > Following up on the bug I posted the other day about incorrect > timestamps, the FreeBSD team are wondering if it might be caused by > conflicting PostgreSQL instances in different FreeBSD jails on the same > host machine. > > However, we've noticed no other problems with this configuration over > the last several and I was under the impression this is a fairly common > scenario. > > Is anyone able to verify or deny that PostgreSQL instances in different > jails (each with their own IP address) will not corrupt each other? I'm > aware they allocate shared memory from a "global pool" of it as made > available on the host system, but have been under the impression > PostgreSQL is coded to not corrupt in this kind of situation. > > Regards and best wishes, > > Justin Clift > > > -------- Original Message -------- > Subject: Re: misc/72498: Libc timestamp code on jailed SMP machine > generates incorrect results > Date: Mon, 11 Oct 2004 09:33:38 +0200 > From: Uwe Doering > Organization: Private UNIX Site > To: Justin Clift > CC: freebsd-gnats-submit@FreeBSD.org > References: <200410110202.i9B228Ye060291@www.freebsd.org> > > Justin Clift wrote: > >> >>> Environment: >> >> >> FreeBSD was-dev.telstra.net 4.10-RELEASE FreeBSD 4.10-RELEASE #0: Fri >> Jun 25 14:23:42 EST 2004 >> root@verdelho.telstra.net:/usr/src/sys/compile/1GB_SHARED_V3 i386 >> >>> Description: >> >> >> We're using PostgreSQL 7.4.5 in an SMP jailed environment on FreeBSD >> 4.10. >> >> Inside this jail PostgreSQL is configured to output timestamp >> information in it's log file entries. There appears to be a bug in >> the timestamp generation code, as for hours above 9 oclock (10am and >> onwards) the timestamp's being generated are occasionally incorrect: >> [...] > > > Do you happen to run more than one instance of PostgreSQL on that > machine, each in its own jail? If so, are you aware that jails don't > have separate SysV shared resources (memory regions etc.), at least not > in FreeBSD's original 4.x implementation? In this scenario your problem > might be caused by clashing PostgreSQL instances, and you're likely to > be in for more serious problems than just time stamp corruption. > > Just an educated guess, of course. > > Uwe