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 1imGf3-0006lu-Kk for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Dec 2019 12:30:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1imGf1-0004Et-7c for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Dec 2019 12:30:07 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1imGf0-0004El-UO for pgsql-hackers@lists.postgresql.org; Tue, 31 Dec 2019 12:30:06 +0000 Received: from www3.webmail.pair.com ([66.39.3.34]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1imGey-0002EW-G2 for pgsql-hackers@postgresql.org; Tue, 31 Dec 2019 12:30:06 +0000 Received: from rc.webmail.pair.com (localhost [127.0.0.1]) by www3.webmail.pair.com (Postfix) with ESMTP id 453443E0062; Tue, 31 Dec 2019 07:30:01 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 31 Dec 2019 13:30:01 +0100 From: Tels To: Robert Haas Cc: Suraj Kharage , Rushabh Lathia , David Steele , Andrew Dunstan , PostgreSQL Hackers , Jeevan Chalke , vignesh C Subject: Re: backup manifests Reply-To: nospam-pg-abuse@bloodgate.com In-Reply-To: References: <4b6244ea-4094-9055-080b-7afb274bf270@pgmasters.net> <146910fc-3df7-eeb4-ac5b-2f57a01f646f@pgmasters.net> <2f4dd3b8-fc39-7a34-d0e3-17fc14e041ea@pgmasters.net> User-Agent: Roundcube Webmail/1.4.0 Message-ID: X-Sender: nospam-pg-abuse@bloodgate.com Organization: Highly Unorganized List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Moin, sorry for the very late reply. There was a discussion about the specific format of the backup manifests, and maybe that was already discussed and I just overlooked it: 1) Why invent your own format, and not just use a machine-readable format that already exists? It doesn't have to be full blown XML, or even JSON, something simple as YAML would already be better. That way not everyone has to write their own parser. Or maybe it is already YAML and just the different keywords where under discussion? 2) It would be very wise to add a version number to the format. That will making an extension later much easier and avoids the "we need to add X, but that breaks compatibility with all software out there" situations that often arise a few years down the line. Best regards, and a happy New Year 2020 Tels