From: | Raimon Fernandez <coder(at)montx(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Cancelling Requests Frontend/Backend Protocol TCP/IP |
Date: | 2009-11-02 17:17:01 |
Message-ID: | 039EEE67-5182-4D48-812D-90DFBB2A4634@montx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg사설 토토SQL Postg윈 토토SQL : Postg윈 |
On 02/11/2009, at 17:53, Tom Lane wrote:
> Raimon Fernandez <coder(at)montx(dot)com> writes:
>> The sentence 'backend has finished processing the query' means that
>> postgresql has finished processing the select and also has sent all
>> the rows ?
>
> There is no distinction; rows are sent as they are generated.
Yes, but a SELECT can return 50000 rows, and as you say, postgresql
sends the rows as they are generated.
My question still remain unclear to me:
when postgres has finished processing the select, just before sending
the first row(1), in the middle(2), or at the end(3), when the last
row has been sent ?
If I send the CancelRequest when postgres is in point 3, I'm too late,
but if postgres is in 1 or 2, the CancelRequest will have some effect.
I'm still wrong here ?
thanks for clarification the concept!
regards,
raimon
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-11-02 17:21:21 | Re: Absolute value of intervals |
Previous Message | Steve Atkins | 2009-11-02 17:06:00 | Re: Error on compile for Windows |
From | Date | Subject | |
---|---|---|---|
Next Message | John DeSoi | 2009-11-02 19:01:11 | Re: Cancelling Requests Frontend/Backend Protocol TCP/IP |
Previous Message | Tom Lane | 2009-11-02 16:53:58 | Re: Cancelling Requests Frontend/Backend Protocol TCP/IP |