From owner-freebsd-bugs@FreeBSD.ORG Tue Oct 12 01:00:52 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0418D16A4CE for ; Tue, 12 Oct 2004 01:00:52 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCE8D43D53 for ; Tue, 12 Oct 2004 01:00:51 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i9C10pYC087073 for ; Tue, 12 Oct 2004 01:00:51 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9C10pCw087072; Tue, 12 Oct 2004 01:00:51 GMT (envelope-from gnats) Date: Tue, 12 Oct 2004 01:00:51 GMT Message-Id: <200410120100.i9C10pCw087072@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Justin Clift Subject: [Fwd: Re: misc/72498: Libc timestamp code on jailed SMP machinegenerates incorrect results] X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Justin Clift List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2004 01:00:52 -0000 The following reply was made to PR misc/72498; it has been noted by GNATS. From: Justin Clift To: pgsql-bugs@postgresql.org Cc: Uwe Doering , freebsd-gnats-submit@FreeBSD.org Subject: [Fwd: Re: misc/72498: Libc timestamp code on jailed SMP machine generates incorrect results] Date: Tue, 12 Oct 2004 10:47:30 +1000 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 -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers gemini@geminix.org | http://www.escapebox.net