Re: backup manifests

--jIk0QLZ6qhbNwLah
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Greetings,

* David Fetter ([email protected]) wrote:
> On Tue, Jan 14, 2020 at 12:53:04PM -0500, Tom Lane wrote:
> > Robert Haas <[email protected]> writes:
> > > ... I would also expect that depending on an external package
> > > would provoke significant opposition. If we suck the code into core,
> > > then we have to keep it up to date with the upstream, which is a
> > > significant maintenance burden - look at all the time Tom has spent on
> > > snowball, regex, and time zone code over the years.
> >=20
> > Also worth noting is that we have a seriously bad track record about
> > choosing external packages to depend on.  The regex code has no upstream
> > maintainer anymore (well, the Tcl guys seem to think that *we* are
> > upstream for that now), and snowball is next door to moribund.
> > With C not being a particularly hip language to develop in anymore,
> > it wouldn't surprise me in the least for any C-code JSON parser
> > we might pick to go dead pretty soon.
>=20
> Given jq's extreme popularity and compatible license, I'd nominate that.

I don't think that really changes Tom's concerns here about having an
"upstream" for this.

For my part, I don't really agree with the whole "we don't want two
different JSON parsers" when we've got two of a bunch of stuff between
the frontend and the backend, particularly since I don't really think
it'll end up being *that* much code.

My thought, which I had expressed to David (though he obviously didn't
entirely agree with me since he suggested the other options), was to
adapt the pgBackRest JSON parser, which isn't really all that much code.

Frustratingly, that code has got some internal pgBackRest dependency on
things like the memory context system (which looks, unsurprisingly, an
awful lot like what is in PG backend), the error handling and logging
systems (which are different from PG because they're quite intentionally
segregated from each other- something PG would benefit from, imv..), and
Variadics (known in the PG backend as Datums, and quite similar to
them..).

Even so, David's offered to adjust the code to use the frontend's memory
management (*cough* malloc()..), and error handling/logging, and he had
some idea for Variadics (or maybe just pulling the backend's Datum
system in..?  He could answer better), and basically write a frontend
JSON parser for PG without too much code, no external dependencies, and
to make sure it answers this requirement, and I've agreed that he can
spend some time on that instead of pgBackRest to get us through this, if
everyone else is agreeable to the idea.  Obviously this isn't intended
to box anyone in- if there turns out even after the code's been written
to be some fatal issue with using it, so be it, but we're offering to
help.

Thanks,

Stephen

--jIk0QLZ6qhbNwLah
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJeHiYbAAoJEO1sijiDR2RV+dYQAKn/DShEVFbWNGYd1z7BTxqE
LNg1uTB1DoMdGrnHiAtDy90V/kV+lGUeRkpL5IBiSgGxpZQw7VddEQJK6BE403sG
AqW7ymk5JPCVCTyE6cVmB8FvRd3WF5vPMzOmFCi2VHTkOmXggGLTVDA5rp8br+pV
t0kuqGL0s+TFsF2toTLwzN9hQI1gN/PmIY9DQeY2PiiAmnl3TPMQYVw3SesRGMQL
J7JgsUGFltTtH+hWNodLfjpPKXHDjI+4RDKBs9C1rfjFc8GtXZ6Bum2/SpC8LjkI
62lGs8h2fhOHKrnw16H3QdUI8sgss09uibMcLARoFwt+z6jNSbMRUvKA4i9gikvb
sMiwGHvfAPSUgjwi6myxClCCHLhdpg4MLCWoHMMdsB+Uxn3rY8SBi70Lol5HBOZu
Z1lnwHUxOTOSLuAvIhi3oCdxmXRMzYriLW7pIrno9eXpXnRJYq2hu7JkyVVf8xc2
8rOHCMsDG2DFprKrJh0f587Y+OrACfqhIl2JHQDuUWH+Qix0ePCWveeVdtSD/np6
mFPLKT89YaSpUDzYr7WlTlMinGZ0uK79FUinxomadOd6LiqldmXVA6c4+uBn70tT
rkogj9QOMkUMGAy5bKwTJKah1MYeub0zN8FnKGYMkrVir8YMbUxxY3ZghD3eURTn
M5++Ocnq4DJD+FLQA7ov
=PV0g
-----END PGP SIGNATURE-----

--jIk0QLZ6qhbNwLah--