Thanks Tom.
That sounds good to me.
On Wed, Jul 17, 2019 at 10:17 AM Tom Lane wrote:
> vignesh C writes:
> > I'm able to get the same behaviour in centos as well.
> > Should we do anything to handle this in Postgres or any documentation
> > required?
>
> It already is documented:
>
> PSQL_P
vignesh C writes:
> I'm able to get the same behaviour in centos as well.
> Should we do anything to handle this in Postgres or any documentation
> required?
It already is documented:
PSQL_PAGER
PAGER
If a query's results do not fit on the screen, they are piped
through
I'm able to get the same behaviour in centos as well.
Should we do anything to handle this in Postgres or any documentation
required?
On Wed, Jul 17, 2019 at 10:05 AM Tom Lane wrote:
> Thomas Munro writes:
> > Pretty sure this is coming from your system's pager. You can see the
> > same thing
Thomas Munro writes:
> Pretty sure this is coming from your system's pager. You can see the
> same thing when you run this on a RHEL box:
> seq 1 1 | more
> It skips a line each time you press ^F.
Yeah, duplicated on RHEL6. It seems to behave the same as the documented
"s" command. Not sur
On Wed, Jul 17, 2019 at 4:07 PM vignesh C wrote:
> One observation when we execute a select query having results more than the
> screen space available and press ctrl+f to display the remaining records, one
> of the record was not displayed and the message "...skipping one line" was
> displayed
Hi,
One observation when we execute a select query having results more than the
screen space available and press ctrl+f to display the remaining records,
one of the record was not displayed and the message "...skipping one line"
was displayed.
I'm not sure if this is intentional behaviour.
Steps
