"Tom Lane" <tgl@xxxxxxxxxxxxx> writes: > BTW, have you looked into the theory that it's triggered by total > data volume rather than number of columns? That is, try selecting > all the columns but use LIMIT to reduce the number of rows fetched? Or conversely select the first or second half of the columns but put two copies of them in the column list. Are the client and server on two separate machines? Is it possible you have a network issue between these two machines (like pmtud problems, for example)? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
