Re: group locking: incomplete patch, just for discussion - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: group locking: incomplete patch, just for discussion
Date
Msg-id 545BF030.3060209@BlueTreble.com
Whole thread Raw
In response to Re: group locking: incomplete patch, just for discussion  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 11/5/14, 8:26 PM, Robert Haas wrote:
> rhaas=# create table foo (a int);
> CREATE TABLE
> rhaas=# select
test_group_locking('1.0:start,2.0:start,1.0:lock:AccessExclusiveLock:foo,2.0:lock:AccessExclusiveLock:foo');
> NOTICE:  starting worker 1.0
> NOTICE:  starting worker 2.0
> NOTICE:  instructing worker 1.0 to acquire AccessExclusiveLock on
> relation with OID 16387
> NOTICE:  instructing worker 2.0 to acquire AccessExclusiveLock on
> relation with OID 16387

Damn that's cool to see! :)

FWIW, some creative use of a composite type, plpgsql and string_to_array() would have saved a bunch of parsing code...
it'ssurprisingly easy to parse stuff like this using string_to_array().
 
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BRIN indexes - TRAP: BadArgument
Next
From: Jim Nasby
Date:
Subject: Re: Tweaking Foreign Keys for larger tables