pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: David Steele <david@pgmasters.net>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: David Fetter <david@fetter.org>
Cc: Tels <nospam-pg-abuse@bloodgate.com>
Cc: Suraj Kharage <suraj.kharage@enterprisedb.com>
Cc: Rushabh Lathia <rushabh.lathia@gmail.com>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Jeevan Chalke <jeevan.chalke@enterprisedb.com>
Cc: vignesh C <vignesh21@gmail.com>
Subject: Re: backup manifests
Date: Tue, 14 Jan 2020 12:53:04 -0500
Message-ID: <12445.1579024384@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+TgmoYdEEtO9HEPdDjV8DUT+=haZf_3bsMEuVgkOWTjt+PSKA@mail.gmail.com>
References: <20200101190917.GR32763@fetter.org>
	<7437.1577925975@sss.pgh.pa.us>
	<CA+TgmoY+U30wCcxD6gLM9kFduMTGGwB1Ei06znLDqTqzcb+38A@mail.gmail.com>
	<30229.1577931611@sss.pgh.pa.us>
	<20200103164424.GW3195@tamriel.snowman.net>
	<CA+TgmoY_icSH_uoBUQH2NnJBucShKsfONCXxdhuLh4m4aAh5Sg@mail.gmail.com>
	<20200103170123.GX3195@tamriel.snowman.net>
	<CA+TgmobjkosrwPaEA6nxhC-JoZ4JGXSiQ+27Zkm3iMY0VnMwvQ@mail.gmail.com>
	<20200103193559.GY3195@tamriel.snowman.net>
	<CA+TgmoY1EpREir7QvAHBzyj370-+bmfFV2F_X3ZDytpxf=iezw@mail.gmail.com>
	<20200108013348.GF3195@tamriel.snowman.net>
	<00b28009-3781-4c4a-174b-be2c1bc52f27@pgmasters.net>
	<CA+TgmoYdEEtO9HEPdDjV8DUT+=haZf_3bsMEuVgkOWTjt+PSKA@mail.gmail.com>

Robert Haas <robertmhaas@gmail.com> 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.

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.

Between that problem and the likelihood that we'd need to make
significant code changes anyway to meet our own coding style etc
expectations, I think really we'd have to assume that we're going
to fork and maintain our own copy of any code we pick.

Now, if it's a small enough chunk of code (and really, how complex
is JSON parsing anyway) maybe that doesn't matter.  But I tend to
agree with Robert's position that it's a big ask for this patch
to introduce a frontend JSON parser.

			regards, tom lane





view thread (243+ messages)  latest in thread

Message-ID: <12445.1579024384@sss.pgh.pa.us>
Permalink:  ../12445.1579024384@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12445.1579024384@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, david@pgmasters.net, sfrost@snowman.net, david@fetter.org, nospam-pg-abuse@bloodgate.com, suraj.kharage@enterprisedb.com, rushabh.lathia@gmail.com, andrew.dunstan@2ndquadrant.com, jeevan.chalke@enterprisedb.com, vignesh21@gmail.com
  Subject: Re: backup manifests
  In-Reply-To: <12445.1579024384@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox