| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Returning SELECTed rows immediately instead of all at the end? |
| Date: | 2020-06-13 11:33:36 |
| Message-ID: | e0ce0b5d-f0e3-f70f-80c2-6205088a5ad0@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 6/13/20 12:10 AM, Tom Lane wrote:
> Ron <ronljohnsonjr(at)gmail(dot)com> writes:
>> I'm running amcheck on a set of indices (test machine, not prod) and want to
>> track the progress. Is there a SELECT clause that makes rows display as
>> they are created, or do I have to explicitly call bt_index_check() from a
>> shell script or SQL function in order to see the output as each index is
>> checked?
> If you're willing to code at the libpq level, see
>
> https://www.postgresql.org/docs/current/libpq-single-row-mode.html
An option (maybe "-r") for psql to put it in single row mode would be useful
for DBAs.
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2020-06-13 11:34:52 | Re: Returning SELECTed rows immediately instead of all at the end? |
| Previous Message | Adrian Klaver | 2020-06-13 05:11:00 | Re: Fwd: not able to give usage access to public schema |