Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vr451-0000XG-IQ for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Dec 2013 11:05:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Vr451-0002YT-0p for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Dec 2013 11:05:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vr44z-0002WW-6I for pgsql-hackers@postgresql.org; Thu, 12 Dec 2013 11:05:17 +0000 Received: from mail.anarazel.de ([217.115.131.40]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vr44s-0000lc-Mt for pgsql-hackers@postgresql.org; Thu, 12 Dec 2013 11:05:16 +0000 Received: from intern.anarazel.de (p5DDC452F.dip0.t-ipconnect.de [93.220.69.47]) (Authenticated sender: andres@anarazel.de) by mail.anarazel.de (Postfix) with ESMTPSA id 46A8E4E8003; Thu, 12 Dec 2013 12:05:07 +0100 (CET) Date: Thu, 12 Dec 2013 12:05:05 +0100 From: Andres Freund To: Simon Riggs Cc: KONDO Mitsumasa , Pavel Stehule , =?iso-8859-1?Q?Fabr=EDzio?= Mello , Robert Haas , Pgsql Hackers Subject: Re: Time-Delayed Standbys Message-ID: <20131212110505.GA14510@alap2.anarazel.de> References: <52A59D10.7020209@lab.ntt.co.jp> <52A5A17D.5010504@lab.ntt.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Pg-Spam-Score: -2.6 (--) 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 On 2013-12-12 09:09:21 +0000, Simon Riggs wrote: > >> * Add functionality (I propose) > >> We can set negative number at min_standby_apply_delay. I think that > >> this feature > >> is for world wide replication situation. For example, master server is > >> in > >> Japan and slave server is in San Francisco. Japan time fowards than > >> San > >> Francisco time > >> . And if we want to delay in this situation, it can need negative > > This is because local time is recorded in XLOG. And it has big cost for > > calculating global time. Uhm? Isn't the timestamp in commit records actually a TimestampTz? And thus essentially stored as UTC? I don't think this problem actually exists? > My suggestion would be to add the TZ to the checkpoint record. This > way all users of WAL can see the TZ of the master and act accordingly. > I'll do a separate patch for that. Intuitively I'd say that might be useful - but I am not reall sure what for. And we don't exactly have a great interface for looking at a checkpoint's data. Maybe add it to the control file instead? Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers