A.M. wrote: > > On Feb 27, 2008, at 9:11 AM, Florian G. Pflug wrote: >> The reason that I'd love some within-one-backend solution is that I'd >> allow you to utilize more than one CPU for a restore within a *single* >> transaction. This is something that a client-side solution won't be >> able to deliver, unless major changes to the architecture of postgres >> happen first... > > It seems like multiple backends should be able to take advantage of 2PC > for transaction safety.
Yeah, but it wouldn't take advantage of, say, the hack to disable WAL when the table was created in the same transaction. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---------------------------(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
