Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eqOMr-0005L8-My for pgsql-docs@arkaria.postgresql.org; Mon, 26 Feb 2018 19:23:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1eqOMq-0000Le-P5 for pgsql-docs@arkaria.postgresql.org; Mon, 26 Feb 2018 19:23:20 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1eqOMq-0000LQ-JV for pgsql-docs@lists.postgresql.org; Mon, 26 Feb 2018 19:23:20 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eqOMn-00011n-VO for pgsql-docs@lists.postgresql.org; Mon, 26 Feb 2018 19:23:20 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w1QJNEXD000324; Mon, 26 Feb 2018 14:23:14 -0500 From: Tom Lane To: Craig Ringer cc: Steve Atkins , pgsql-docs@lists.postgresql.org Subject: Re: Images in the official documentation In-reply-to: References: <1914747379.117313.1519402446241.JavaMail.zimbra@dbi-services.com> <08B83F11-EB17-4436-B73A-1857898B6B9B@blighty.com> <22981.1519618609@sss.pgh.pa.us> Comments: In-reply-to Craig Ringer message dated "Mon, 26 Feb 2018 14:30:31 +0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <322.1519672994.1@sss.pgh.pa.us> Date: Mon, 26 Feb 2018 14:23:14 -0500 Message-ID: <323.1519672994@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Craig Ringer writes: > On 26 February 2018 at 12:16, Tom Lane wrote: >> How can we resolve these issues? > Question the assumptions and requirements. Why do we actually _need_ > diffable, mergeable images? Sure, it'd be *nice*, but what's the real world > impact if we don't have it? Well, I'll tell you exactly why I'm being sticky about this: we've been down this road before. We used to have some figures in .gif format, and one of the problems with them was they were too hard to update. I don't buy the "they won't need updates" argument for a second, either. For instance, I recall that one of the images we had was a diagram of the system catalog cross-references, and it was constantly out of date because of the difficulty of updating it. Admittedly, this was 15+ years ago. Maybe the state of the art in figure editors has advanced to the point where it won't be so hard. But color me suspicious. regards, tom lane