Обсуждение: devx article
Hi all, reading this article: http://www.devx.com/dbzone/Article/20743 I notice on page 2: "New versions of PostgreSQL support standard row-level locking as an option, but MVCC is the preferred method" What this does mean ? Regards Gaetano Mendola
On Sat, Aug 21, 2004 at 01:15:29AM +0200, Gaetano Mendola wrote: > http://www.devx.com/dbzone/Article/20743 > > I notice on page 2: > > "New versions of PostgreSQL support standard row-level > locking as an option, but MVCC is the preferred method" > > What this does mean ? Or this one: "MySQL does, however, support the advanced feature of data partitioning within a database. PostgreSQL does not." Isn't that what tablespaces are all about? Jeroen
> > > Or this one: > > "MySQL does, however, support the advanced feature of data partitioning > within a database. PostgreSQL does not." > > Isn't that what tablespaces are all about? Well there is table partitioning and then there is tablespaces. PostgreSQL 8 supports table spaces but not table partitioning. J > > > Jeroen > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Вложения
"Joshua D. Drake" <jd@commandprompt.com> writes: >> "MySQL does, however, support the advanced feature of data partitioning >> within a database. PostgreSQL does not." > Well there is table partitioning and then there is tablespaces. > PostgreSQL 8 supports table spaces but not table partitioning. Note that it's possible to roll-your-own table partitioning in PG, using either views of table unions or inheritance. It's not going to be as simple to use as a hard-wired implementation, but on the other hand you might have more flexibility to tune it to your needs. You can find reports in the archives from people doing exactly this sort of thing. The above quote is undoubtedly copied straight from some MySQL marketing materials, rather than being the result of any serious investigation. regards, tom lane