From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Raimon Fernandez <coder(at)montx(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Cancelling Requests Frontend/Backend Protocol TCP/IP |
Date: | 2009-11-02 16:35:32 |
Message-ID: | 4881.1257179732@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-interfaces |
Raimon Fernandez <coder(at)montx(dot)com> writes:
> Quoted from the documentation:
> "The cancellation signal might or might not have any effect for
> example, if it arrives after the
> backend has nished processing the query, then it will have no
> effect.
> Here I understand that maybe it will have NO effect, so postgresql
> will still sending rows and rows and rows ...
If you're too late, the backend has already sent all the rows. There's
not much we can do about data that's already in flight. There probably
won't be that much of it though, as TCP stacks don't buffer infinite
amounts of data.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2009-11-02 16:37:42 | Re: Cancelling Requests Frontend/Backend Protocol TCP/IP |
Previous Message | joeweder | 2009-11-02 16:20:52 | 8.4 initdb failure |
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2009-11-02 16:37:42 | Re: Cancelling Requests Frontend/Backend Protocol TCP/IP |
Previous Message | Raimon Fernandez | 2009-11-02 15:52:15 | Re: Cancelling Requests Frontend/Backend Protocol TCP/IP |