Postgres Pro
Downloads
Home   >   mailing lists

Re: Let's invent a function to report lock-wait-blocking PIDs - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Let's invent a function to report lock-wait-blocking PIDs
Date
Msg-id CA+U5nMJ1bJ41hYL2r5zqSt_5PNcXbSwv-YeNsVKZ1Zjjc2QpiA@mail.gmail.com
Whole thread Raw
In response to Let's invent a function to report lock-wait-blocking PIDs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Let's invent a function to report lock-wait-blocking PIDs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On 20 March 2013 18:02, Tom Lane <tgl@sss.pgh.pa.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

pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)
Next
From: Simon Riggs
Date:
Subject: Re: Should commit_delay be PGC_SIGHUP?