Re: rename sgml files?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: rename sgml files?
Date: 2018-02-12 23:38:36
Message-ID: 21504.1518478716@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Fetter <david(at)fetter(dot)org> writes:
> On Mon, Feb 12, 2018 at 04:19:48PM -0500, Tom Lane wrote:
>> As I've remarked before, the issue would disappear if we were to
>> back-patch the XML-ization of the documentation. So I'd be fine
>> with this if we did it uniformly in the supported branches. Otherwise
>> I think the costs outweigh the benefits.

> +1 for back-patching.

> Are there scripts for (at least the first cut of) this?

IIRC, Peter said basically that it was more work than he cared to tackle,
which I guess means that there was significant manual effort involved.

The most practical answer might be to wait a few years till all the live
branches use XML, and then we can do the renaming in all branches
trivially. Perhaps finishing the XML conversion in v10 would be cheap
enough that it'd be worth doing that to shave one year off the wait.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-02-12 23:55:11 Re: In logical replication concurrent update of partition key creates a duplicate record on standby.
Previous Message Andrew Dunstan 2018-02-12 23:34:52 Re: Disabling src/test/[ssl|ldap] when not building with SSL/LDAP support