Re: mysql proxy

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-advocacy(at)postgresql(dot)org
Cc: Lukas Kahwe Smith <smith(at)pooteeweet(dot)org>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
Subject: Re: mysql proxy
Date: 2007-08-27 17:40:33
Message-ID: 200708271040.34213.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

Andreas, Lukas,

> >> I am sure most of you have seen some blog post [1] on the mysql proxy
> >> [2]. It basically allows you to proxy calls to the server. Inside the
> >> proxy you can write scripts (language is LUA) to do all sorts of funky
> >> things like auditing, r/w splitting by master/slave [2], connection
> >> pooling etc.
> >
> > Sounds like mysql-proxy tries to mimic what pgsql's triggers and rules
> > and pgpool already do.

No, I don't think that's accurate.

> If that is the case, it might be worth it to write a comparison blog
> post illustrating that this is available for PostgreSQL. I wasnt aware
> that there is a scripting language embedded in pgpool.

There isn't AFAIK.

The current "best of" proxies for PostgreSQL is pgBouncer. I'd be interested
in seeing us add scripting capabilities to it like MySQL has; it seems like a
cool idea. Of course, I personally have no plans to do the work.

--
Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Josh Berkus 2007-08-27 18:04:13 Re: The naming question WAS: Theme of this release: Performance?
Previous Message Lukas Kahwe Smith 2007-08-27 17:25:25 Re: mysql proxy