Re: Time limit for a process to hold Content lock in Buffer Cache

From: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Time limit for a process to hold Content lock in Buffer Cache
Date: 2013-05-23 15:50:19
Message-ID: CAOeZVifCh0sWeL+KYxahtZFrusb-zK8HPJZVt=jm3_LPBoQs+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Right, the actual signal handler will only kill the query immediately
> if the backend is in a safe state (eg, while it's waiting for a
> heavyweight lock). Otherwise it just sets a flag that's checked by
> CHECK_FOR_INTERRUPTS. See StatementCancelHandler in postgres.c.

Roger that, I will definitely have a look and ask if I have any questions.

Thanks a ton!

Regards,

Atri

--
Regards,

Atri
l'apprenant

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-05-23 16:14:10 Re: pg_rewind, a tool for resynchronizing an old master after failover
Previous Message Tom Lane 2013-05-23 15:49:07 Re: Time limit for a process to hold Content lock in Buffer Cache