Hello,
For what I've read in the manuals, this operation is only valid before
PostgreSQL has finished processing the SELECT statement ?
If for example I send a SELECT * from myTable, it has 2 rows, and
postgre starts sending the rows, how I can cancel this operation ?
I thought
On 2/11/2009 5:15 PM, Raimon Fernandez wrote:
For what I've read in the manuals, this operation is only valid before
PostgreSQL has finished processing the SELECT statement ?
If for example I send a SELECT * from myTable, it has 2 rows, and
postgre starts sending the rows, how I can
On 02/11/2009, at 10:29, Craig Ringer wrote:
On 2/11/2009 5:15 PM, Raimon Fernandez wrote:
For what I've read in the manuals, this operation is only valid
before
PostgreSQL has finished processing the SELECT statement ?
If for example I send a SELECT * from myTable, it has 2 rows,
On Nov 2, 2009, at 4:15 AM, Raimon Fernandez wrote:
If for example I send a SELECT * from myTable, it has 2 rows,
and postgre starts sending the rows, how I can cancel this operation ?
I thought Cancelling Requests would be perfect for this ... the
workaround is closing and opening
Craig Ringer cr...@postnewspapers.com.au writes:
On 2/11/2009 5:15 PM, Raimon Fernandez wrote:
If for example I send a SELECT * from myTable, it has 2 rows, and
postgre starts sending the rows, how I can cancel this operation ?
Assuming you're asking is there any way to cancel a running
On 02/11/2009, at 15:38, Tom Lane wrote:
Craig Ringer cr...@postnewspapers.com.au writes:
On 2/11/2009 5:15 PM, Raimon Fernandez wrote:
If for example I send a SELECT * from myTable, it has 2 rows,
and
postgre starts sending the rows, how I can cancel this operation ?
Assuming
On 02/11/2009, at 15:12, John DeSoi wrote:
On Nov 2, 2009, at 4:15 AM, Raimon Fernandez wrote:
If for example I send a SELECT * from myTable, it has 2 rows,
and postgre starts sending the rows, how I can cancel this
operation ?
I thought Cancelling Requests would be perfect for
Raimon Fernandez co...@montx.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
On 2/11/2009 10:38 PM, Tom Lane wrote:
Craig Ringer cr...@postnewspapers.com.au writes:
On 2/11/2009 5:15 PM, Raimon Fernandez wrote:
If for example I send a SELECT * from myTable, it has 2 rows, and
postgre starts sending the rows, how I can cancel this operation ?
Assuming you're
On 02/11/2009, at 17:35, Tom Lane wrote:
Raimon Fernandez co...@montx.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 finished processing the query, then it will have no
effect.
Here I
Raimon Fernandez co...@montx.com writes:
The sentence 'backend has ï¬nished 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.
regards, tom
On 02/11/2009, at 17:53, Tom Lane wrote:
Raimon Fernandez co...@montx.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.
On Nov 2, 2009, at 12:17 PM, Raimon Fernandez wrote:
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
On 02/11/2009, at 20:01, John DeSoi wrote:
On Nov 2, 2009, at 12:17 PM, Raimon Fernandez wrote:
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
14 matches
Mail list logo
