[wp-hackers] Porting Wordpress to PostgreSQL

[Martin]

Don't know too much about the internals of postgres query caching but I do
know that I like the end result. =)

I am in a similar boat as the others as far as why I want to use postgres,
it's what we have at the office. We are phasing mysql completely out and
wordpress its one of the last applications left. I could go on about why I
like postgres over mysql but as mentioned that's kinda pointless in this
case as I'm not developing against it.

But I can speak to this, "I can't imagine that the effort to port to another
SQL dialect would be cheaper than throwing hardware at the deployment."
It's back to the standards thing. It's not so much that we would be porting
to another specific SQL dialect, but instead be porting to a portable SQL
dialect.
Port once use on many different systems, Oracle, Postgres, MySQL, MSSQL.
Then let your customers choose what to run your application on. It's a nice
feature that allows for more flexibility, it's not really a performance
thing (although I'm sure some would argue otherwise=] ).

I would be very willing to contribute some time to this effort, by writing
SQL, PHP code and/or documentation.


On 3/23/06, Carson Evans < carson at digitalambit.com> wrote:
>
>
> On Mar 22, 2006, at 5:57 PM, Andrew Krespanis wrote:
>
> > *wonders where  the postgre guys went :-? *
>
> I'd consider myself a "postgres guy" because I like it and want to
> see WP work well with it, but that doesn't mean In understand how it
> handles query cacheing. :)
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>