Re: pgsql --echo-errors --quiet and setval

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Les <nagylzs(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql --echo-errors --quiet and setval
Date: 2023-09-08 20:11:18
Message-ID: d7d3a40e-61f1-2045-b5ab-6521a7da62bd@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 9/8/23 12:36, Les wrote:
>
>   Dear fellow PostgreSQL users,
>
> Today I caught this with postgresql v15, while restoring a database with
> psql  --echo-errors --quiet. (The dump was made using pg_dump -Fp).
>
> It logged lots of these messages:
>
>  setval
> --------
>    1001
> (1 row)
>
> In other words, it logs **some** things that are not errors, even though
> --quiet was specified. Is this the expected behaviour? I would argue
> that with --quiet --echo-errors, only errors should be logged, and
> setting the value of a sequence is not an error.

No but SELECT pg_catalog.setval(...) in the dump file is a function that
has return value and that is what you are seeing.

>
> Thank you,
>
>     Laszlo
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2023-09-08 22:01:50 Re: pgsql --echo-errors --quiet and setval
Previous Message Les 2023-09-08 19:36:11 pgsql --echo-errors --quiet and setval