From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Alex Turner <armtuk(at)gmail(dot)com>, Jason McManus <mcmanus(dot)jason(at)gmail(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Notes on converting from MySQL 5.0.x to PostgreSQL |
Date: | 2006-07-11 15:57:19 |
Message-ID: | 1152633439.6540.65.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-www |
On Tue, 2006-07-11 at 10:45, Jan Wieck wrote:
> On 7/10/2006 10:00 PM, Alex Turner wrote:
>
> > http://dev.mysql.com/doc/refman/5.1/en/replication-row-based.html
> >
> > 5.1
>
> Ah, thanks. So I guess 5.1.5 and 5.1.8 must be considered major feature
> minor/bugfix releases. I still don't understand how people can use
> software in production that has literally zero bugfix upgrade path
> without the risk of incompatibility due to new features. I consider
> every IT manager, who makes that choice, simply overpaid.
Dear god! That page made my eyes bleed.
Individual users can choose the method of replication for their
sessions?
There's a mixed method that switches back and forth?
"In addition to switching the logging format manually, a slave server
may switch the format automatically."
I'm pretty sure this kind of thing would never get into PostgreSQL.
It's like reading a map of a minefield drawn in crayon.
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2006-07-11 16:04:07 | Re: pgsql vs mysql |
Previous Message | Vance Maverick | 2006-07-11 15:49:28 | SQL parsing suggestions? |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2006-07-11 17:07:43 | Re: Notes on converting from MySQL 5.0.x to PostgreSQL |
Previous Message | Jan Wieck | 2006-07-11 15:45:31 | Re: Notes on converting from MySQL 5.0.x to PostgreSQL |