| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Les <nagylzs(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql --echo-errors --quiet and setval |
| Date: | 2023-09-08 22:01:50 |
| Message-ID: | CAKFQuwbzKMJW4F2enc6rL4VP2o2bAj5v9EcfsoCTfXUZGtAPuw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Sep 8, 2023 at 1:41 PM Les <nagylzs(at)gmail(dot)com> 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.
>
The output of SELECT queries cannot be quieted, only redirected.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2023-09-09 07:31:09 | Re: postgreSQL UPPER Method is converting the character "µ" into "M" |
| Previous Message | Adrian Klaver | 2023-09-08 20:11:18 | Re: pgsql --echo-errors --quiet and setval |