PATCHES] selecting large result sets in psql using cursors)
>
> I've always been
> quite amazed how much email some of the folks here manage to
> process... I
> suppose I could just chalk it up to a pine vs. gui thing, but
> I suspect there
> are some other tricks peo
On Aug 23, 2006, at 12:15 , Robert Treat wrote:
On Thursday 17 August 2006 11:55, Peter Eisentraut wrote:
Tom Lane wrote:
Yeah, that experiment hasn't seemed to work all that well for me
either. Do you have another idea to try, or do you just want to
revert to the old way?
Since almost the
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Robert Treat wrote:
>> ... some other tricks people have to make emails more manageable (anyone
>> combine all pg mail to one folder?)
> Yes, all mine are in one folder, and I use elm ME. It is faster than a
> GUI email client.
All my PG list mail go
On Thursday 17 August 2006 11:55, Peter Eisentraut wrote:
> Tom Lane wrote:
> > Yeah, that experiment hasn't seemed to work all that well for me
> > either. Do you have another idea to try, or do you just want to
> > revert to the old way?
>
> Since almost the first day I hacked on PostgreSQL I ha
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Chris Mair wrote:
>> Since buffer commands all have a single char I wanted a single char one
>> too. The "c" for "cursor" was taken already, so i choose the "u" (second
>> char in "cursor"). If somebody has a better suggestion, let us know ;)
> I think a
On Thu, Aug 17, 2006 at 09:20:43AM -0400, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Ever since pgsql-patches replies started going to -hackers, threading
> > doesn't work anymore, so I for one can't tell what this refers to at
> > all.
>
> Yeah, that experiment hasn't se
Tom Lane wrote:
> Yeah, that experiment hasn't seemed to work all that well for me
> either. Do you have another idea to try, or do you just want to
> revert to the old way?
Since almost the first day I hacked on PostgreSQL I have been filtering
both lists into the same folder, so they pretty mu
Hi,
thanks for reviewing this :)
> > attached is the new and fixed version of the patch for selecting
> > large result sets from psql using cursors.
>
> The is_select_command bit is wrong because it doesn't allow for left
> parentheses in front of the SELECT keyword (something entirely
> reasona
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Ever since pgsql-patches replies started going to -hackers, threading
> doesn't work anymore, so I for one can't tell what this refers to at
> all.
Yeah, that experiment hasn't seemed to work all that well for me
either. Do you have another idea to
Tom Lane wrote:
> BTW, \u seems not to have any mnemonic value whatsoever ... isn't
> there some other name we could use?
Ever since pgsql-patches replies started going to -hackers, threading
doesn't work anymore, so I for one can't tell what this refers to at
all.
--
Peter Eisentraut
http://d
Chris Mair <[EMAIL PROTECTED]> writes:
> attached is the new and fixed version of the patch for selecting
> large result sets from psql using cursors.
The is_select_command bit is wrong because it doesn't allow for left
parentheses in front of the SELECT keyword (something entirely
reasonable when
11 matches
Mail list logo
