| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BUG #17212: pg_amcheck fails on checking temporary relations |
| Date: | 2021-10-11 18:33:40 |
| Message-ID: | CAH2-Wzk=-VD25g02gwoKCW1kLC2QrJC94agoPaAwywwr_Tvzvw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, Oct 11, 2021 at 11:29 AM Mark Dilger
<mark(dot)dilger(at)enterprisedb(dot)com> wrote:
> The recently submitted patch already contains a short paragraph for each of these, but not a warning box. Should I reformat those as warning boxes? I don't know the current thinking on the appropriateness of that documentation style.
I definitely think that it warrants a warning box. This is a huge
practical difference.
Note that I'm talking about a standard thing, which there are
certainly a dozen or more examples of in the docs already. Just grep
for "<warning> </warning>" tags to see the existing warning boxes.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2021-10-11 18:37:15 | Re: BUG #17212: pg_amcheck fails on checking temporary relations |
| Previous Message | Mark Dilger | 2021-10-11 18:29:12 | Re: BUG #17212: pg_amcheck fails on checking temporary relations |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2021-10-11 18:37:15 | Re: BUG #17212: pg_amcheck fails on checking temporary relations |
| Previous Message | Mark Dilger | 2021-10-11 18:29:12 | Re: BUG #17212: pg_amcheck fails on checking temporary relations |