On Sun, Nov 10, 2019 at 05:45:08PM +0800, Craig Ringer wrote:
> On Sun, 10 Nov 2019 at 13:42, Tom Lane wrote:
>
> > Andres Freund writes:
> > > On 2019-11-08 14:49:25 +0800, Craig Ringer wrote:
> > >> I recently found the need to pretty-print the contents of pg_locks. So
> > >> here's a little
On Sun, 10 Nov 2019 at 13:42, Tom Lane wrote:
> Andres Freund writes:
> > On 2019-11-08 14:49:25 +0800, Craig Ringer wrote:
> >> I recently found the need to pretty-print the contents of pg_locks. So
> >> here's a little helper to do it, for anyone else who happens to have
> that
> >> need.
Andres Freund writes:
> On 2019-11-08 14:49:25 +0800, Craig Ringer wrote:
>> I recently found the need to pretty-print the contents of pg_locks. So
>> here's a little helper to do it, for anyone else who happens to have that
>> need. pg_identify_object is far from adequate for the purpose. Reckon
Hi,
On 2019-11-08 14:49:25 +0800, Craig Ringer wrote:
> I recently found the need to pretty-print the contents of pg_locks. So
> here's a little helper to do it, for anyone else who happens to have that
> need. pg_identify_object is far from adequate for the purpose. Reckon I
> should turn it
Hi all
I recently found the need to pretty-print the contents of pg_locks. So
here's a little helper to do it, for anyone else who happens to have that
need. pg_identify_object is far from adequate for the purpose. Reckon I
should turn it into C and submit?
CREATE FUNCTION describe_pg_lock(IN
