Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZZaC-0001rC-6d for pgsql-hackers@arkaria.postgresql.org; Thu, 11 Jan 2018 09:55:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZZaB-0002sW-PM for pgsql-hackers@arkaria.postgresql.org; Thu, 11 Jan 2018 09:55:35 +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 1eZZaB-0002sE-FH for pgsql-hackers@lists.postgresql.org; Thu, 11 Jan 2018 09:55:35 +0000 Received: from forward103j.mail.yandex.net ([2a02:6b8:0:801:2::106]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eZZa8-0002FM-2n for pgsql-hackers@postgresql.org; Thu, 11 Jan 2018 09:55:34 +0000 Received: from mxback19j.mail.yandex.net (mxback19j.mail.yandex.net [IPv6:2a02:6b8:0:1619::95]) by forward103j.mail.yandex.net (Yandex) with ESMTP id B3DD134C0E5F; Thu, 11 Jan 2018 12:55:29 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback19j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id g4oOWyE8NJ-tRKChNA4; Thu, 11 Jan 2018 12:55:28 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zsrv.org; s=mail; t=1515664528; bh=ol3xXc8ROJ/5gsYMh1GeoqBwYnZ0NqNLbuk1AdynYOg=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date; b=fL33dBovvgn17xaC+IO62II0rj05c5ZhIHvpTz7ySQwYtajOoV5L+kbeoV9VC+ZGX cXDC8HklzpiY27QS1lVPCCPPadyWH3KLYN3fu7nyPEuQWcviqFaqI9xzyUc02K6Q5g H6Kd/vLHNs2a4ossIaSQcCg1ux2k8fIi+dd28HTM= Authentication-Results: mxback19j.mail.yandex.net; dkim=pass header.i=@zsrv.org Received: by web40g.yandex.ru with HTTP; Thu, 11 Jan 2018 12:55:27 +0300 From: Sergei Kornilov To: Kyotaro HORIGUCHI Cc: "michael.paquier@gmail.com" , "andres@anarazel.de" , "peter.eisentraut@2ndquadrant.com" , "pgsql-hackers@postgresql.org" In-Reply-To: <20180111.155910.26212237.horiguchi.kyotaro@lab.ntt.co.jp> References: <20171222.150320.244267360.horiguchi.kyotaro@lab.ntt.co.jp> <337571513944260@web55j.yandex.ru> <20180111.155910.26212237.horiguchi.kyotaro@lab.ntt.co.jp> Subject: Re: [HACKERS] Restricting maximum keep segments by repslots MIME-Version: 1.0 Message-Id: <2798121515664527@web40g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Thu, 11 Jan 2018 12:55:27 +0300 Content-Transfer-Encoding: 7bit Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello >> patch -p1 gives some "Stripping trailing CRs from patch" >> messages for me, but applied to current HEAD and builds. After > > Hmm. I wonder why I get that complaint so often. (It's rather > common? or caused by the MIME format of my mail?) I'd say with > confidence that it is because you retrieved the patch file on > Windows mailer. I use Debian and web based mailer. Hm, i wget patches from links here https://www.postgresql.org/message-id/flat/20180111.155910.26212237.horiguchi.kyotaro%40lab.ntt.co.jp - applies clean both last and previous messages. Its strange. Updated patches builds ok, but i found one failed test in make check-world: contrib/test_decoding/sql/ddl.sql at the end makes SELECT * FROM pg_replication_slots; which result of course was changed And i still have no better ideas for naming. I think on something like if (min_keep_lsn <= restart_lsn) if (active_pid != 0) status = "streaming"; else status = "keeping"; else status = "may_lost"; This duplicates an existing active field, but I think it's useful as slot status description. wal_status streaming/keeping/lost/unknown as described in docs patch is also acceptable for me. Maybe anyone else has better idea? Regards, Sergei