I'm afraid I don't actually think there's a way to do this. Postprocess searches are applied to all of the rows, and although postprocess searches can arbitrarily transform and change the results into some other set of rows, ultimately the pagination is always going to just page row-wise through those rows.
If you could accept a restriction that the number of rows were fixed at some number like 10, then we could hack some of this use case, in that we could use the search language to create "fields" for the first N days on rows 1-10, and then fields starting at 2N-1 for rows 11-20, fields corresponding to the next days starting at row 21 etc. Then when you paged through the rows, the column headers would appear to change.
But as for the broader question of making the "results per page" turn into "columns per page", pagination and postprocess would have to work fundamentally differently to do so.
... View more
