Re: pg_input_error_info doc 2 exampled crammed together

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_input_error_info doc 2 exampled crammed together
Date: 2024-04-29 01:45:30
Message-ID: CAKFQuwbyXQ2LHrN5Vabcutnrv=zOLGfp2_t79__cccWm5OnHww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday, April 28, 2024, jian he <jian(dot)universality(at)gmail(dot)com> wrote:
>
>
> after checking the definition of <programlisting>[1], <screen>[2],
> maybe here we should use <screen>

>
Possibly, though I’d be curious to see how consistent we are on this point
elsewhere before making a point of it.

>
> and also add `(1 row)` information.

Doesn’t seem like added value.

>
> or we can simply add a empty new line between
> ` value "42000000000" is out of range for type integer | | |
> 22003`
> and
> `</programlisting>`

My preference would be to limit this section to a single example. The
numeric one, as it provides values for more output columns. I would change
the output format to expanded from default, in order to show all columns
and not overrun the length of a single line.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2024-04-29 02:50:00 Re: POC: GROUP BY optimization
Previous Message wenhui qiu 2024-04-29 01:36:58 Re: Support "Right Semi Join" plan shapes