Comments on: WordPress and PostgreSQL http://thoughts.davisjeff.com/2009/07/30/wordpress-and-postgresql/ Ideas on Databases, Logic, and Language by Jeff Davis Tue, 19 Jun 2012 16:18:51 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jeff Davis http://thoughts.davisjeff.com/2009/07/30/wordpress-and-postgresql/comment-page-1/#comment-180 Jeff Davis Sun, 07 Mar 2010 19:24:26 +0000 http://davisjeff.wordpress.com/?p=31#comment-180 Oh, great! I'll give it a shot. I may start hosting it myself soon, which would be a good opportunity to try it. Oh, great!

I’ll give it a shot. I may start hosting it myself soon, which would be a good opportunity to try it.

]]>
By: Hawk__ http://thoughts.davisjeff.com/2009/07/30/wordpress-and-postgresql/comment-page-1/#comment-173 Hawk__ Mon, 18 Jan 2010 19:55:54 +0000 http://davisjeff.wordpress.com/?p=31#comment-173 Wow ! How strange :) I've just noticed this post which you published just one month after I published the first release of my "plugin" to allow using WordPress with a PostgreSQL. Maybe you'd like to give it a try ? You can find it in the WordPress plugins directory : http://wordpress.org/extend/plugins/postgresql-for-wordpress/ Just a note : for now the development version is the only one to support WordPress 2.9.1 until I have enough feedback about it working in different setups. Wow ! How strange :)

I’ve just noticed this post which you published just one month after I published the first release of my “plugin” to allow using WordPress with a PostgreSQL.

Maybe you’d like to give it a try ?

You can find it in the WordPress plugins directory :

http://wordpress.org/extend/plugins/postgresql-for-wordpress/

Just a note : for now the development version is the only one to support WordPress 2.9.1 until I have enough feedback about it working in different setups.

]]>
By: Michael http://thoughts.davisjeff.com/2009/07/30/wordpress-and-postgresql/comment-page-1/#comment-118 Michael Mon, 02 Nov 2009 16:57:53 +0000 http://davisjeff.wordpress.com/?p=31#comment-118 apologies, I got the address wrong. The right URL is http://habariproject.org/ apologies, I got the address wrong. The right URL is http://habariproject.org/

]]>
By: Michael http://thoughts.davisjeff.com/2009/07/30/wordpress-and-postgresql/comment-page-1/#comment-117 Michael Mon, 02 Nov 2009 16:53:01 +0000 http://davisjeff.wordpress.com/?p=31#comment-117 Dear Jeff, Habari works with MySQL, PostgreSQL and SQLite and it's developed by people who get blogging (ex-Wordpress fans). http://habari.org/ Dear Jeff,

Habari works with MySQL, PostgreSQL and SQLite and it’s developed by people who get blogging (ex-Wordpress fans).

http://habari.org/

]]>
By: Document Scanning Washington http://thoughts.davisjeff.com/2009/07/30/wordpress-and-postgresql/comment-page-1/#comment-109 Document Scanning Washington Fri, 23 Oct 2009 12:52:20 +0000 http://davisjeff.wordpress.com/?p=31#comment-109 Wordpress is having great features like importing all the required data which is very helpful retrieving the data. :) WordPress is having great features like importing all the required data which is very helpful retrieving the data. :)

]]>
By: Rob Wultsch http://thoughts.davisjeff.com/2009/07/30/wordpress-and-postgresql/comment-page-1/#comment-68 Rob Wultsch Tue, 04 Aug 2009 06:32:02 +0000 http://davisjeff.wordpress.com/?p=31#comment-68 Howdy, I think you are oversimplifying what people expect from publishing systems. Consider "Tags" and site analytics which are generally quite relational in implementation. Full text search on myisam is very much out of favor by power users as it is fairly slow and not particularly tunable. Sphinix is a popular alternative and there is a MySQL interface with Sphinix which allows to MySQL to make use of its far superior implementation. From the work I had done with WordPress I get the feeling that the developers don't want to think all that much about relational theory. Turning on the general query log while installing WordPress make some of the ugliness of the system visible. Cheers, Rob Howdy,

I think you are oversimplifying what people expect from publishing systems. Consider “Tags” and site analytics which are generally quite relational in implementation.

Full text search on myisam is very much out of favor by power users as it is fairly slow and not particularly tunable. Sphinix is a popular alternative and there is a MySQL interface with Sphinix which allows to MySQL to make use of its far superior implementation.

From the work I had done with WordPress I get the feeling that the developers don’t want to think all that much about relational theory. Turning on the general query log while installing WordPress make some of the ugliness of the system visible.

Cheers,

Rob

]]>
By: How to Bring Import and Export Back « Experimental Thoughts http://thoughts.davisjeff.com/2009/07/30/wordpress-and-postgresql/comment-page-1/#comment-29 How to Bring Import and Export Back « Experimental Thoughts Fri, 31 Jul 2009 04:28:51 +0000 http://davisjeff.wordpress.com/?p=31#comment-29 [...] Experimental Thoughts Ideas on Databases, Logic, and Language by Jeff Davis « Wordpress and PostgreSQL [...] [...] Experimental Thoughts Ideas on Databases, Logic, and Language by Jeff Davis « WordPress and PostgreSQL [...]

]]>
By: Christopher Browne http://thoughts.davisjeff.com/2009/07/30/wordpress-and-postgresql/comment-page-1/#comment-28 Christopher Browne Thu, 30 Jul 2009 17:56:38 +0000 http://davisjeff.wordpress.com/?p=31#comment-28 Another benefit to PostgreSQL support would be TOAST... http://www.postgresql.org/docs/8.4/static/storage-toast.html I think TOAST would be *enormously* helpful for a "large text field"-oriented application like WordPress, from three perspectives: a) Compressing the large text columns should diminish I/O considerably b) Compression reduces the overall footprint of the database, and should reduce memory usage, too c) By separating the "big text" bits into TOAST tables, queries that don't actually access those bits will fit *wildly* more tuples into each page (of disk/memory), and be spectacularly more efficient Another benefit to PostgreSQL support would be TOAST…
http://www.postgresql.org/docs/8.4/static/storage-toast.html

I think TOAST would be *enormously* helpful for a “large text field”-oriented application like WordPress, from three perspectives:

a) Compressing the large text columns should diminish I/O considerably

b) Compression reduces the overall footprint of the database, and should reduce memory usage, too

c) By separating the “big text” bits into TOAST tables, queries that don’t actually access those bits will fit *wildly* more tuples into each page (of disk/memory), and be spectacularly more efficient

]]>