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:34:52 |
Message-ID: | 53616aa4-a363-a672-ce3b-d72cd302ef1b@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6/13/20 12:04 AM, David G. Johnston wrote:
> On Friday, June 12, 2020, Ron <ronljohnsonjr(at)gmail(dot)com
> <mailto:ronljohnsonjr(at)gmail(dot)com>> wrote:
>
>
> 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,
>
>
> No
>
> 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?
>
>
> You could wrap the function call in a custom plpgsql function (or just do
> a plpgsql loop) and side channel output via notice but i’d probably just
> do a shell script wrapper absent any other constraint.
Yeah, a shell script was my next option. Thanks.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2020-06-13 11:53:28 | Re: Something else about Redo Logs disappearing |
Previous Message | Ron | 2020-06-13 11:33:36 | Re: Returning SELECTed rows immediately instead of all at the end? |