Re: pgsql/src backend/tcop/postgres.c include/misc ... - Mailing list pgsql-committers

From Hiroshi Inoue
Subject Re: pgsql/src backend/tcop/postgres.c include/misc ...
Date
Msg-id EKEJJICOHDIEMGPNIFIJAEPNGFAA.Inoue@tpf.co.jp
Whole thread Raw
In response to Re: pgsql/src backend/tcop/postgres.c include/misc ...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql/src backend/tcop/postgres.c include/misc ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
>
> Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> > ExecProcNode doesn't return unless
> > it finds a tuple which satisfies the qualification.
>
> Oh, of course you are right.  I guess there should be
> CHECK_FOR_INTERRUPTS in the per-tuple loops of nodeSeqscan.c
> and nodeIndexscan.c, as well.  Joins should be okay, since they
> get their inputs from lower-level ExecProcNode calls.

Now I realize that 7.1 already changed the handling of
die interrupts fundamentally. For example we can't kill
the backend which is in a trouble with an infinite loop.
Was it an intended change ?

regards,
Hiroshi Inoue

pgsql-committers by date:

Previous
From: barry@postgresql.org
Date:
Subject: pgsql/src/interfaces/jdbc/org/postgresql jdbc1 ...
Next
From: Tom Lane
Date:
Subject: Re: pgsql/src backend/tcop/postgres.c include/misc ...