Re: Let's invent a function to report lock-wait-blocking PIDs

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Let's invent a function to report lock-wait-blocking PIDs
Date: 2013-03-21 00:20:18
Message-ID: CA+U5nMJ1bJ41hYL2r5zqSt_5PNcXbSwv-YeNsVKZ1Zjjc2QpiA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20 March 2013 18:02, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The API that comes to mind is (name subject to
> bikeshedding)
>
> pg_blocking_pids(pid int) returns int[]
>

Useful. Can we also have an SRF rather than an array?

Does the definition as an array imply anything about our ability to
join an SRF to an array?

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2013-03-21 00:22:42 Re: Should commit_delay be PGC_SIGHUP?
Previous Message David E. Wheeler 2013-03-20 23:52:34 Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)