From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Review: support for multiplexing SIGUSR1 |
Date: | 2009-07-17 20:30:10 |
Message-ID: | 3073cc9b0907171330t74065a39q8a95b8599d7d6521@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 17, 2009 at 1:44 PM, Jaime
Casanova<jcasanov(at)systemguards(dot)com(dot)ec> wrote:
>
> i wasn't able to repeat this on a new instalation and of
> course i can't swear this is your patch fault...
>
this is not your patch fault but an existing bug, i repeat that
behaviour in an unpatched source tree...
with the steps in the previous mail i canceled 2 or 3 backend before
cancell the one with the explain analyze, i execute a second time that
pg_cancel_backend and if i try to re-run the query it gets cancelled
immediately, next time it runs normally...
pg_stat_activity reports that query as running no mather what...
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
From | Date | Subject | |
---|---|---|---|
Next Message | Alan Li | 2009-07-17 20:35:33 | MIN/MAX optimization for partitioned table |
Previous Message | Dickson S. Guedes | 2009-07-17 20:24:16 | Re: WIP patch for TODO Item: Add prompt escape to display the client and server versions |