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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-10 17:50:29
Message-ID: CAKFQuwabDn3Op_gQdmqz2_rk_6G57kFx3p+k-yjBZv0UHUs_DQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Sep 10, 2023 at 10:43 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I'm not sure whether it'd be profitable to try to build that behavior
>
into the scripts themselves.

Teaching it not to call "print" (or making it a no-op somehow) in a certain
mode, yes, trying to redirect output it is producing, I doubt it for the
reason mentioned. It isn't difficult to add "> /dev/null" to the command
line if that is what you want - no need to touch scripts given a capable
enough shell.

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message gzh 2023-09-11 04:57:39 Re: ERROR: stack depth limit exceeded
Previous Message Tom Lane 2023-09-10 17:43:25 Re: pgsql --echo-errors --quiet and setval