On Thu, Oct 12, 2006 at 03:03:43PM -0400, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > The specific concern I have is large result sets, like 10s or 100s of MB > > (or more). We just added support for not buffering those in psql, so it > > seems like a step backwards to have the backend now buffering it (unless > > I'm confused on how a tuplestore works...) > > Well, a tuplestore can dump to disk, so at least you don't need to worry > about out-of-memory considerations.
Sure, it's just a lot of data to be shuffling around if we can avoid it. Perhaps we could only do this if there's triggers on the table involved? -- Jim Nasby [EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
