Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZhbNN-0006Qh-QM for pgsql-docs@arkaria.postgresql.org; Thu, 01 Oct 2015 10:46:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZhbNN-0007CQ-CU for pgsql-docs@arkaria.postgresql.org; Thu, 01 Oct 2015 10:46:13 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZhbNL-0007BF-RL; Thu, 01 Oct 2015 10:46:12 +0000 Received: from mail-qk0-x22c.google.com ([2607:f8b0:400d:c09::22c]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZhbNE-0006Fn-VM; Thu, 01 Oct 2015 10:46:10 +0000 Received: by qkap81 with SMTP id p81so30066902qka.2; Thu, 01 Oct 2015 03:46:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WCVZIPlkP5rL5O43WVwUdkKdOgrsq73XOu4lSshR+fM=; b=DdyS2xPOnoGltRYRxcOnYPsqWJfpDkueE36ZJgs0CeJLZubbccdKyKUYtMO+Mw0Ujo w6bKT3S6U43S8LkasoScBd6h+BCfYO9ywiuUbo/HflV6G8/nnEoMbUTCb0ovyG7OBRZi L6YGtulObqAvFv3+hvB6oIR70iN5sbBTPuc6Dvr1lE+YoKJX8be8/fH5iS5PqVuh4cmk tYmpHYGZIpg3g5rcLCtemKPSdnpFAK9WovqRLtK+2xDgGjqyHubkj5SvtJvCE5OAp4TS eMZzYoiryEXSEi9g0hrI98YacCDl0C6gVcOUVkIwo4Be+oIkM3feeIK2+pTlR0ZT5LtH hNYQ== MIME-Version: 1.0 X-Received: by 10.55.201.198 with SMTP id m67mr11009467qkl.35.1443696364343; Thu, 01 Oct 2015 03:46:04 -0700 (PDT) Received: by 10.55.44.7 with HTTP; Thu, 1 Oct 2015 03:46:04 -0700 (PDT) In-Reply-To: <20150930224806.GR2573@alvherre.pgsql> References: <20150930224806.GR2573@alvherre.pgsql> Date: Thu, 1 Oct 2015 19:46:04 +0900 Message-ID: Subject: Re: max_worker_processes on the standby From: Fujii Masao To: Alvaro Herrera Cc: oonishitk@nttdata.co.jp, pgsql-docs , PostgreSQL-development Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Thu, Oct 1, 2015 at 7:48 AM, Alvaro Herrera wrote: > oonishitk@nttdata.co.jp wrote: > >> The below error messages were shown in standby server log: >> >> FATAL: could not access status of transaction 9009 >> DETAIL: Could not read from file "pg_commit_ts/0000" at offset 90112: Success. >> CONTEXT: xlog redo Transaction/COMMIT: 2015-09-30 15:52:41.924141+09 >> LOG: startup process (PID 23199) exited with exit code 1 >> LOG: terminating any other active server processes >> >> Before this FATAL, there were some INFO but annoying messages: >> >> LOG: file "pg_commit_ts/0000" doesn't exist, reading as zeroes > > Here's a patch. I've not read the patch yet, but the patched server with track_commit_timestamp enabled caused the following PANIC error when I ran pgbench. PANIC: could not access status of transaction 2457 DETAIL: Could not read from file "pg_commit_ts/0000" at offset 24576: Success. STATEMENT: END; The procedure to reproduce the PANIC error is, 1. Enable track_commit_timestamp 2. Start up the server 3. Run pgbench -i -s10 4. Run pgbench -j 4 -c 4 -T 30 Regards, -- Fujii Masao -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs