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: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_input_error_info doc 2 exampled crammed together
Date: 2024-04-29 05:07:49
Message-ID: CAKFQuwY1YLOEgWRPd20dEqLSi8QT8uu0yBSm3=faDk99F=qW7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday, April 28, 2024, Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> On Sun, Apr 28, 2024 at 06:45:30PM -0700, David G. Johnston wrote:
> > 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.
>
> Agreed that having two examples does not bring much, so this could be
> brought to a single one. The first one is enough to show the point of
> the function, IMO. It is shorter in width and it shows all the output
> columns.
>
>
Agreed. The column names are self-explanatory if you’ve seen errors
before. The values are immaterial. Plus we don’t generally use
psql-specific features in our examples.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-04-29 05:11:00 Re: A failure in prepared_xacts test
Previous Message Alexander Lakhin 2024-04-29 05:00:00 Re: A failure in prepared_xacts test