Re: Let's invent a function to report lock-wait-blocking PIDs
| От | Tom Lane |
|---|---|
| Тема | Re: Let's invent a function to report lock-wait-blocking PIDs |
| Дата | |
| Msg-id | 804.1363836984@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Let's invent a function to report lock-wait-blocking PIDs (Simon Riggs <simon@2ndQuadrant.com>) |
| Ответы |
Re: Let's invent a function to report lock-wait-blocking
PIDs
Re: Let's invent a function to report lock-wait-blocking PIDs |
| Список | 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 по дате отправления: