From: | gabrielle <gorthx(at)gmail(dot)com> |
---|---|
To: | Postgresql PDX_Users <pdxpug(at)postgresql(dot)org> |
Subject: | February meeting next week |
Date: | 2012-02-10 23:51:13 |
Message-ID: | CAHRs-_dHL-+zMFQaEGc4OO55Hyf=AoHKGGS+yq4aSyaABHPauw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pdxpug |
When: 7-9pm Thu Feb 16, 2012
Where: Iovation
Who: John Melesky
What: Locks... etc.
High-traffic systems have to deal with locks. That's just the way it
is. But that's okay! Locks invisibly help manage concurrency! Properly
structured transactions will never run into deadlocks with each other!
Right?
Well, sometimes locks are very visible, and sometimes you end up with
deadlocks that don't make sense. I'm going to talk through a couple of
row-locking problems i've run into, and explain how and why that
should end up changing PostgreSQL's SQL syntax.
John's been poking computers since he was old enough to type, which
was long enough ago that he debated whether to make a "POKEing" joke.
He's a Software Engineer at Janrain, working with the reporting and
analytics infrastructure.
Our meeting will be held at Iovation, on the 32nd floor of the US
Bancorp Tower at 111 SW 5th (5th & Oak). It's right on the Green &
Yellow Max lines. Underground bike parking is available in the
parking garage; outdoors all around the block in the usual spots. No
bikes in the office, sorry!
Building security will close access to the floor at 7:30.
After-meeting beer location TBD. See you there!
From | Date | Subject | |
---|---|---|---|
Next Message | Tim | 2012-03-05 19:02:20 | Portland OWASP Chapter Meeting - March 8 |
Previous Message | Mark Wong | 2012-01-19 17:22:47 | Fwd: January meeting coming up |