On Fri, Aug 18, 2006 at 10:16:12AM -0400, Tom Lane wrote: > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > A \set variable would make sense to me. > > So Peter and Bruce like a \set variable, Chris and I like a different > command. Seems like a tie ... more votes out there anywhere?
If this will be used interactively, it would be nice to have both. That way if you're running a bunch of cursor fetches, you can just do one \set, but if you only want to run one or a few you can use \gc and not mess around with \set. But I don't know how common interactive usage will be. Presumably code can easily be taught to do either, though \set would probably be less invasive to older code that someone wants to change. Another thought (which probably applies more to \set than \gc): if you could set a threshold of how many rows the planner is estimating before automatically switching to a cursor, that would simplify things. Interactively, you could just let psql/PostgreSQL decide which was best for each query. Same is true in code, though it probably matters more for existing code than new code. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster