Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gR31Y-0002Np-8j for pgsql-hackers@arkaria.postgresql.org; Sun, 25 Nov 2018 22:37:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gR31W-0004Zw-Lc for pgsql-hackers@arkaria.postgresql.org; Sun, 25 Nov 2018 22:37:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gR31W-0004Zo-B9 for pgsql-hackers@lists.postgresql.org; Sun, 25 Nov 2018 22:37:06 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gR31T-0002Eq-Dj for pgsql-hackers@postgresql.org; Sun, 25 Nov 2018 22:37:04 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 4FD135F7A2; Sun, 25 Nov 2018 17:37:02 -0500 (EST) Date: Sun, 25 Nov 2018 17:37:02 -0500 From: Stephen Frost To: Sergei Kornilov Cc: Andres Freund , Peter Eisentraut , Michael Paquier , PostgreSQL mailing lists Subject: Re: Continue work on changes to recovery.conf API Message-ID: <20181125223702.GR3415@tamriel.snowman.net> References: <943181539360922@iva4-24c534b4e3ac.qloud-c.yandex.net> <32159921540906216@myt5-9da6df248f4a.qloud-c.yandex.net> <51a6446c-c2b6-b653-c9f5-da38e23ddd9d@2ndquadrant.com> <22367601542121030@iva5-d3020dc3459d.qloud-c.yandex.net> <2d1877b6-e8cf-a27c-4608-c40758dd0f6c@2ndquadrant.com> <20181121060012.GE1951@paquier.xyz> <20181125182415.GP3415@tamriel.snowman.net> <20181125203927.f66lvh55ef5aw65g@alap3.anarazel.de> <7003801543178959@sas1-46c84f197234.qloud-c.yandex.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="saqwZB8dd8xoGD4q" Content-Disposition: inline In-Reply-To: <7003801543178959@sas1-46c84f197234.qloud-c.yandex.net> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --saqwZB8dd8xoGD4q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings, * Sergei Kornilov (sk@zsrv.org) wrote: > > Why don't we put recovery entries into postgresql.recovery.conf or such? > > And overwrite rather than append? > Appending to postgressql.auto.conf instead of writing new hardcoded file was proposed here: https://www.postgresql.org/message-id/CAB7nPqQ-Grduc-0WSsK4-VXo%2B1CB%3DyDS9NMU0NEp%2Bc%2Bffnz0UQ%40mail.gmail.com Thanks, yes, I saw that but I don't think it really contemplated the issues that arise from that approach, as I outlined. Thanks again! Stephen --saqwZB8dd8xoGD4q Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJb+yQNAAoJEO1sijiDR2RVyW4P+wXaKisH/7YSUJlf0z6uYvGN 5+0jF6m9okHglx+FN0ZfSHMwb1E59g+eYAZh3BIvPwfIJoYKoca5PsljSe4r9tOi 5fIthR371MeTwb+532OdC0L2FDJFZM2rmQVhOl/nZJ+dtna4wKk5nOX83YJ1JP3s GiKOQoY+PboaJAYVDncKg5ifAr7XTSKEr388b2ft01PudSNciBP+I61T0IF35o5n ZVEPFIz8WZLq9TP0lR6XQsrrjMZ1pwZGiDHYe9IV0xJgVe9x7Hn1vOJf1c2+l2rc YHEDv2uXKtZOtbiXLPOrE91D4c53f1IsdE0QgEHcjJFf3a7n84VHiNFhDwgQHp8e p7H+OwnAnD21AP3faDgrp5WuKnl36X4gFsrYJFyiEGUohwJcRukdVxe2OgQyxR3R uZIXUsLpswjAKVL4ybGkNfdQZVF3/AIR3MpIR97dlgmt8BTvHgCy757r2zL4A0qz OKzXPWKvFyg4au32l8evYC6MYnaqlFxXW8M0GPPGj9LFwbcdfjSEDJCjemajlJDh 4Wpr/4q9LTlsjZpWICpkhqPPvAR1iv82nAqq00LXx1j3TfVPkmiqEVE5mZDULbFF t9U+000Vdjx02CEe0CGxJVrUw9WU5JdEzVx6HQF9zh+rcT3pqi70KQL9zKIwz3iG jI/uDATIDlo31s3H1JP9 =Coq4 -----END PGP SIGNATURE----- --saqwZB8dd8xoGD4q--