On Thu, Mar 26, 2009 at 5:10 PM, Scott Marlowe <scott.marlowe@xxxxxxxxx> wrote: > It's also important to point out that writers don't necessarily block > other writers. As long as they're operating on different ranges of > the data set. You can have dozens of writers streaming data in with > differening primary keys all running together. To be fare, some database apps have a few rows they update in a near continuous stream, and they row lock. These databases are often better served by db2 or some other row locking database than pgsql where you may or may not have problems with bloating. There are times picking a database some will turn left when they should have turned right. Picking pgsql for this kind of app is usually that kind of situation. Innodb would have bloat problems I'd assume too. MyIsam's table locking puts it out, and you're left with one of the other databases. I wonder how firebird handles that situation. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
