2007/10/23, Martijn van Oosterhout <[EMAIL PROTECTED]>:
> On Tue, Oct 23, 2007 at 09:56:26AM +0400, Sergey Konoplev wrote:
> > I took a look at TCP state with netstat:
> >
> > pgdb:/base/PG-Data # netstat -pna |grep 8590
> > tcp1 0 127.0.0.1:5432 127.0.0.1:35442
> > CLOSE_WAIT
On Tue, Oct 23, 2007 at 09:56:26AM +0400, Sergey Konoplev wrote:
> I took a look at TCP state with netstat:
>
> pgdb:/base/PG-Data # netstat -pna |grep 8590
> tcp1 0 127.0.0.1:5432 127.0.0.1:35442
> CLOSE_WAIT 8590/postgres: kono
CLOSE_WAIT means that the client (in this ca
2007/10/17, Sergey Konoplev <[EMAIL PROTECTED]>:
> Hello again,
>
> Sorry for the deal with my answer it was realy hectic week so I
> couldn't even check my mail.
>
> 2007/10/3, Richard Huxton <[EMAIL PROTECTED]>:
> > Sergey Konoplev wrote:
> > >> Don't forget to cc: the list.
> > >> Try not to top
2007/10/3, Erik Jones <[EMAIL PROTECTED]>:
> On Oct 3, 2007, at 6:47 AM, Richard Huxton wrote:
>
> > Sergey Konoplev wrote:
> >>> Don't forget to cc: the list.
> >>> Try not to top-post replies, it's easier to read if you reply
> >>> below the
> >>> text you're replying to.
> >> Thanx for your advi
2007/10/3, Alvaro Herrera <[EMAIL PROTECTED]>:
> Sergey Konoplev escribió:
>
> > > AFAIK, pl/pgsql does listen for SIGINT during execution, but I don't nkow
> > > abuot plpython.
> >
> > How can we find it out?
>
> Let's see one of the functions to find out if anyone else can reproduce
> the proble
Hello again,
Sorry for the deal with my answer it was realy hectic week so I
couldn't even check my mail.
2007/10/3, Richard Huxton <[EMAIL PROTECTED]>:
> Sergey Konoplev wrote:
> >> Don't forget to cc: the list.
> >> Try not to top-post replies, it's easier to read if you reply below the
> >> te
On Oct 3, 2007, at 6:47 AM, Richard Huxton wrote:
Sergey Konoplev wrote:
Don't forget to cc: the list.
Try not to top-post replies, it's easier to read if you reply
below the
text you're replying to.
Thanx for your advice. I'm just absolutely worned out. Sorry.
Know that feeling - let's s
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Does pl/python listen to SIGINT during execution of functions? If not,
> that'd be an explanation - if it's stuck inside a pl/python function...
> AFAIK, pl/pgsql does listen for SIGINT during execution, but I don't nkow
> abuot plpython.
It does not,
Sergey Konoplev escribió:
> > AFAIK, pl/pgsql does listen for SIGINT during execution, but I don't nkow
> > abuot plpython.
>
> How can we find it out?
Let's see one of the functions to find out if anyone else can reproduce
the problem.
--
Alvaro Herrerahttp://w
Sergey Konoplev wrote:
Don't forget to cc: the list.
Try not to top-post replies, it's easier to read if you reply below the
text you're replying to.
Thanx for your advice. I'm just absolutely worned out. Sorry.
Know that feeling - let's see if we can't sort this out.
1. Is it always the sa
> > Don't forget to cc: the list.
> > Try not to top-post replies, it's easier to read if you reply below the
> > text you're replying to.
> >
> > Sergey Konoplev wrote:
> > >>1. Is it always the same query?
> > >>2. Does the client still think it's connected?
> > >>3. Is that query using up CPU, o
On Wed, Oct 03, 2007 at 11:18:32AM +0100, Richard Huxton wrote:
> Don't forget to cc: the list.
> Try not to top-post replies, it's easier to read if you reply below the
> text you're replying to.
>
> Sergey Konoplev wrote:
> >>1. Is it always the same query?
> >>2. Does the client still think it
Don't forget to cc: the list.
Try not to top-post replies, it's easier to read if you reply below the
text you're replying to.
Sergey Konoplev wrote:
1. Is it always the same query?
2. Does the client still think it's connected?
3. Is that query using up CPU, or just idling?
4. Anything odd in
Sergey Konoplev wrote:
I'm sorry I mean not HUP but KILL
Hmm...
datname | usename | procpid | current_query | waiting |
query_start
---+--+-+-+-+---
transport | belostotskaya_la | 20530
I'm sorry I mean not HUP but KILL
2007/10/3, Sergey Konoplev <[EMAIL PROTECTED]>:
> Hi all,
>
> I often face with buzz queries (see below). I've looked through pg
> manual and huge amount of forums and mail archives and found nothing.
> The only solution is to restart postgres server. Moreover I
15 matches
Mail list logo