Re: plpgsql-trigger.html: Format TG_ variables as table (patch)

From: Christoph Berg <myon(at)debian(dot)org>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: plpgsql-trigger.html: Format TG_ variables as table (patch)
Date: 2022-08-31 09:59:29
Message-ID: Yw8xAZhbvlzJR3Jf@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: Peter Eisentraut
> I find the new version even harder to read. The catalog_table_entry stuff
> doesn't really make sense here, since what you have before is already a
> definition list, and afterwards you have the same, just marked up
> "incorrectly".

Fair enough. For comparison, this is what yesterday's patch looked
like: https://www.df7cb.de/s/2022-08-31.115813.w5UvAS.png

> We could move the data type in the <term>, similar to how you did it in your
> patch.

The new version of the patch just moves up the data types, and removes
the extra clutter from the beginnings of each description:

https://www.df7cb.de/s/2022-08-31.115857.LkkKl8.png

Christoph

Attachment Content-Type Size
0001-plpgsql-trigger.html-Use-more-concise-wording-for-TG.patch text/x-diff 6.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Asif Rehman 2022-08-31 10:29:58 Re: [PATCH] Fix alter subscription concurrency errors
Previous Message Daniel Gustafsson 2022-08-31 09:55:50 Re: plpgsql-trigger.html: Format TG_ variables as table (patch)