Postgres Pro
Downloads
Home   >   mailing lists

Re: Time limit for a process to hold Content lock in Buffer Cache - Mailing list pgsql-hackers

From Atri Sharma
Subject Re: Time limit for a process to hold Content lock in Buffer Cache
Date
Msg-id CAOeZVifCh0sWeL+KYxahtZFrusb-zK8HPJZVt=jm3_LPBoQs+Q@mail.gmail.com
Whole thread Raw
In response to Re: Time limit for a process to hold Content lock in Buffer Cache  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
> 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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Time limit for a process to hold Content lock in Buffer Cache
Next
From: Robert Haas
Date:
Subject: Re: pg_rewind, a tool for resynchronizing an old master after failover