| From: | Tels <nospam-pg-abuse(at)bloodgate(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
| Subject: | Re: backup manifests |
| Date: | 2019-12-31 12:30:01 |
| Message-ID: | f97892ef565db763c97f23566c2cb6e5@bloodgate.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-12-31 12:39:36 | Re: pgbench - use pg logging capabilities |
| Previous Message | Juan José Santamaría Flecha | 2019-12-31 12:13:32 | Re: color by default |