Re: controlling psql's use of the pager a bit more

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: controlling psql's use of the pager a bit more
Date: 2015-03-26 15:10:34
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> Without having actually tried it, it looks clean enough to me. If
> there's more pager options we might at some point introduce a pager
> options struct instead adding more options to PageOutput. But for now it
> seems ok enough.

My reaction is that now would be the time to do that, really. This is
messing up the argument lists of what seems like a whole lot of functions,
and I have little faith that this is the last argument we'll need to add.

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-03-26 15:27:32 Re: Re: [COMMITTERS] pgsql: Add macros wrapping all usage of gcc's __attribute__.
Previous Message Andres Freund 2015-03-26 14:13:41 Re: Error with index on unlogged table