Re: Returning SELECTed rows immediately instead of all at the end? - Mailing list pgsql-general

From Ron
Subject Re: Returning SELECTed rows immediately instead of all at the end?
Date
Msg-id 53616aa4-a363-a672-ce3b-d72cd302ef1b@gmail.com
Whole thread Raw
In response to Re: Returning SELECTed rows immediately instead of all at the end?  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
On 6/13/20 12:04 AM, David G. Johnston wrote:
On Friday, June 12, 2020, Ron <ronljohnsonjr@gmail.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.

pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: Returning SELECTed rows immediately instead of all at the end?
Next
From: Laurenz Albe
Date:
Subject: Re: Something else about Redo Logs disappearing