title: best practice, for sql "select" queries that return more than 30k rows - Postgres
body: <p>I have some queries, currently I have a table where we use it to download reports, the query of that table is only a &quot;select&quot; that is searched by date range, it happens that the amount of record that it returns is quite a lot, it is say more than 30k, and I wanted to know if there is a good practice for downloading results that are very heavy in Postgres? For example, concept of data compression or something similar, the idea is that the download of my reports is extremely fast</p>
  <p>Note that I have a B-tree index, for searching by date range.</p>
  <p>I know that indexes are very good for specific queries, but for queries that return many rows, is there any technique to improve performance?</p>