psql lacking clearerr()

2021-03-24 Thread Alvaro Herrera
psql seems to never call clearerr() on its output file. So if it gets an error while printing a result, it'll show could not print result table: Success after each and every result, even though the output file isn't in error state anymore. It seems that the simplest fix is just to do clearerr()

Re: psql lacking clearerr()

2021-03-24 Thread Kyotaro Horiguchi
At Wed, 24 Mar 2021 11:11:41 -0300, Alvaro Herrera wrote in > psql seems to never call clearerr() on its output file. So if it gets > an error while printing a result, it'll show > > could not print result table: Success > > after each and every result, even though the output file isn't in er

Re: psql lacking clearerr()

2021-03-29 Thread Alvaro Herrera
On 2021-Mar-25, Kyotaro Horiguchi wrote: > That worked for me:p And the following steps always raises that error. > > postgres=# select 1; (just to let it into history). > postgres=# C-s -> C-p -> C-m -> C-c > postgres=# select 1; > ... > could not print result table: Success Ah, thanks! Indee

Re: psql lacking clearerr()

2021-03-29 Thread Alvaro Herrera
On 2021-Mar-29, Alvaro Herrera wrote: > (And, yes, I'm to remove the %m too, because clearly that was a mistake.) Re-reading the other thread, I think the %m should stay. -- Álvaro Herrera Valdivia, Chile "I think my standards have lowered enough that now I think 'good design' is when the