Comment 1 for bug 659637

Well, this seems to be an intentional design decision.

The tables mentioned are generated on the fly using the TableFunction interface, if I'm understanding it all correctly. Each time the tables are read, they are "created" and "populated" from another data source. In the transaction log's case, this source is an in-memory object containing all information related to the TL since server startup. It is transient and not persistent across restarts.

Also, this object seems to grow without bounds. :(