Comments on: FeedLounge Switches To PostgreSQL

By: Joseph Scott’s Blog » MySQL to PostgreSQL and UUID/GUIDs

Joseph Scott’s Blog » MySQL to PostgreSQL and UUID/GUIDs — Thu, 08 Dec 2005 21:19:40 +0000

[...] I’ve already mentioned the announcement of FeedLounge making the move from MySQL to PostgreSQL last month, but the discussion is still on going. If you haven’t yet, go read all of the comments on the announcement. This has to be some of the most productive and level headed (no flames yet) set of blog comments I’ve seen in a long time. For those of you who are coming late to this story let me bring you up to speed: [...]

By: jB: no - that's definitely not good enough

jB: no - that's definitely not good enough — Mon, 05 Dec 2005 16:12:22 +0000

Feedlounge switched from MySQL to PostgreSQL for good

Feedlounge, the upcoming web-based feeds reader on steroids mentioned a while back that they switched their db-server from MySQL to PostgreSQL and by doing so, they saved alot of space and reduced their restore times dramatically.

Some of the reason…

By: Daniel

Daniel — Wed, 23 Nov 2005 18:46:06 +0000

Data may get compressed on disk by PostgreSQL, as explained in: http://www.postgresql.org/docs/8.0/static/storage-toast.html
For a database consisting mostly of large text contents, a big shrink in size can probably be achieved by the compression alone.

By: Scott Sanders

Scott Sanders — Mon, 21 Nov 2005 18:06:48 +0000

You forgot to mention the queries running in one third the time on one third the total memory :)

We are looking forward to partial indices (only index the unread items, for instance), as another space/time saving measure.

I will write up more as I get some time on dotnot.org