Re: Add id's to various elements in protocol.sgml

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Brar Piening <brar(at)gmx(dot)de>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add id's to various elements in protocol.sgml
Date: 2021-12-17 07:13:51
Message-ID: f73c1f87-3e9f-06b0-7c1d-3d253dfdb6cd@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 15.12.21 16:59, Brar Piening wrote:
> On Dec 15, 2021 at 15:49, Alvaro Herrera wrote:
>> On 2021-Dec-15, Brar Piening wrote:
>>> Since I can't argue towards some general utility for the xreflabels
>>> and don't have any other solid argument in favor of adding more, I
>>> will remove them from my current patch but leave the existing ones
>>> intact.
>> Yeah, I think not adding them until we have a use for them might be
>> wisest.
> A new version of the patch that doesn't add xreflabels is attached.

Now this patch adds a bunch of ids, but you can't use them to link to,
because as soon as you do, you will get complaints about a missing
xreflabel. So what is the remaining purpose?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shruthi Gowda 2021-12-17 07:33:06 Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce)
Previous Message Peter Eisentraut 2021-12-17 07:03:33 Re: Column Filtering in Logical Replication