This is a discussion on Re: [BUGS] create index concurrently blocks on transactions inother databases within the Pgsql Patches forums, part of the PostgreSQL category; --> On Thu, 2007-09-06 at 21:47 +0100, Simon Riggs wrote: > On Thu, 2007-09-06 at 15:55 -0400, Tom Lane wrote: ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On Thu, 2007-09-06 at 21:47 +0100, Simon Riggs wrote: > On Thu, 2007-09-06 at 15:55 -0400, Tom Lane wrote: > > This would have been painful to fix in 8.2 but it seems relatively > > trivial in HEAD --- we just need another filter option in > > GetCurrentVirtualXIDs. Patch enclosed. Tested manually on same/different databases. No docs changed, nor test cases added. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |
| ||||
| Simon Riggs <simon@2ndquadrant.com> writes: > On Thu, 2007-09-06 at 15:55 -0400, Tom Lane wrote: >> This would have been painful to fix in 8.2 but it seems relatively >> trivial in HEAD --- we just need another filter option in >> GetCurrentVirtualXIDs. > Patch enclosed. Tested manually on same/different databases. > No docs changed, nor test cases added. Applied. I changed the docs thus - addition it must wait for all existing transactions to terminate. Thus + addition it must wait for all existing transactions that could potentially + use the index to terminate. Thus which is a bit vague about the details but perhaps that's just as well. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| Thread Tools | |
| Display Modes | |
|
|