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

From Tom Lane
Subject Re: Let's invent a function to report lock-wait-blocking PIDs
Date
Msg-id 804.1363836984@sss.pgh.pa.us
Whole thread Raw
In response to Re: Let's invent a function to report lock-wait-blocking PIDs  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Let's invent a function to report lock-wait-blocking PIDs  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Re: Let's invent a function to report lock-wait-blocking PIDs  (Jim Nasby <jim@nasby.net>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> 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?

I thought about that, but at least for the isolationtester use-case,
the array result is clearly easier to use.  You can get from one to the
other with unnest() or array_agg(), so I don't really feel a need to
provide both.  Can you generate use-cases where the set-result approach
is superior?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Let's invent a function to report lock-wait-blocking PIDs
Next
From: Magnus Hagander
Date:
Subject: Re: [pgsql-advocacy] Call for Google Summer of Code mentors, admins