On 7/11/2006 11:57 AM, Scott Marlowe wrote:
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/bugf
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 unders
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 literall
http://dev.mysql.com/doc/refman/5.1/en/replication-row-based.html5.1AlexOn 7/10/06,
Jan Wieck <[EMAIL PROTECTED]> wrote:
On 6/30/2006 11:12 AM, Scott Marlowe wrote:> I agree with Tom, nice notes. I noted a few minor issues that seem to> derive from a familiarity with MySQL. I'll put my correctio
On 6/30/2006 11:12 AM, Scott Marlowe wrote:
I agree with Tom, nice notes. I noted a few minor issues that seem to
derive from a familiarity with MySQL. I'll put my corrections below...
On Fri, 2006-06-30 at 08:17, Jason McManus wrote:
On Converting from MySQL 5.0.x to PostgreSQL 8.1.x
---
[EMAIL PROTECTED] ("Jim C. Nasby") writes:
>> Uh oh. I'm a little worried about writing tests based on GPLed code
>> for Slony-I or other replication systems. Might these need to be
>> clean-roomed?
>
> Is there actually a lack of ideas for our regression tests, or a lack of
> people/motivation t
On Friday 30 June 2006 09:17, Jason McManus wrote:
> On Converting from MySQL 5.0.x to PostgreSQL 8.1.x
> * There is a conversion utility called 'mysql2pgsql' that will convert
> dump files from the mysqldump format, to a format that psql can
> understand. It is available at:
> - http://gbor
> -Original Message-
> From: David Fetter [mailto:[EMAIL PROTECTED]
> Sent: 30 June 2006 18:30
> To: Dave Page
> Cc: Scott Marlowe; Jason McManus; pgsql general
> Subject: Re: [GENERAL] Notes on converting from MySQL 5.0.x
> to PostgreSQL
>
> Last I checke
Hmm, not good - I've forwarded this to the techdocs author.
Regards, Dave
-Original Message-
From: "Jason McManus" <[EMAIL PROTECTED]>
To: "Dave Page"
Cc: "pgsql-general@postgresql.org"
Sent: 02/07/06 05:00
Subject: Re: [GENERAL] Notes on conver
Hi Dave,
Documentation such as this can be added to the new techdocs area on the
main site at http://www.postgresql.org/docs/techdocs under the relevant
section (probably http://www.postgresql.org/docs/techdocs.3 in this
case).
Please note that the editting interface is still new and may still
On Fri, Jun 30, 2006 at 11:26:06PM -0400, Tom Lane wrote:
> Something that would actually hold some intellectual interest is to
> improve the testing infrastructure. The current setup is pretty limited
> as to its ability to deal with varying outputs, and even more limited
> in its ability to test
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> Is there actually a lack of ideas for our regression tests, or a lack of
> people/motivation to work on them?
Certainly there are plenty of ideas in the archives ... but writing
regression tests is so *boring* :-(. This is definitely a weak spot
for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Browne wrote:
> [EMAIL PROTECTED] (Ron Johnson) writes:
>
>> Scott Marlowe wrote:
>> [snip]
>>> However, the more interesting thing here, is that every
>>> statement, including DDL is transactable, except for a couple of
>>> big odd ones, like c
On Fri, Jun 30, 2006 at 05:16:46PM -0500, Scott Marlowe wrote:
> This is essentially correct. Note that I can use pgpool with postgresql
> and get about the same behaviour as mysql's replication, with the same
> basic draw backs, that it's best to copy the database between shutdown
> machines, and
On Fri, Jun 30, 2006 at 11:39:04AM -0400, Tom Lane wrote:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
> > On Fri, 2006-06-30 at 08:17, Jason McManus wrote:
> >> * Replication support still rudimentary.
>
> > H. I think that's an overly simplistic evaluation. The slony
> > replication engine
On Fri, Jun 30, 2006 at 11:01:19AM -0700, David Fetter wrote:
> On Fri, Jun 30, 2006 at 01:41:53PM -0400, Tom Lane wrote:
> > David Fetter <[EMAIL PROTECTED]> writes:
> > > On Fri, Jun 30, 2006 at 11:39:04AM -0400, Tom Lane wrote:
> > >> It might be worth pointing out that mysql's replication falls
On Fri, 2006-06-30 at 16:34, Chris Browne wrote:
> [EMAIL PROTECTED] (Scott Marlowe) writes:
> > I agree with Tom, nice notes. I noted a few minor issues that seem to
> > derive from a familiarity with MySQL. I'll put my corrections below...
> >
> > On Fri, 2006-06-30 at 08:17, Jason McManus wrot
[EMAIL PROTECTED] (Scott Marlowe) writes:
> I agree with Tom, nice notes. I noted a few minor issues that seem to
> derive from a familiarity with MySQL. I'll put my corrections below...
>
> On Fri, 2006-06-30 at 08:17, Jason McManus wrote:
>> On Converting from MySQL 5.0.x to PostgreSQL 8.1.x
>>
[EMAIL PROTECTED] (Ron Johnson) writes:
> Scott Marlowe wrote:
> [snip]
>> However, the more interesting thing here, is that every
>> statement, including DDL is transactable, except for a couple of
>> big odd ones, like create database. So, in postgresql, you can do:
>>
>> begin;
>> create table
David Fetter <[EMAIL PROTECTED]> writes:
> On Fri, Jun 30, 2006 at 01:41:53PM -0400, Tom Lane wrote:
>> Sure, it's just the standard "make test" sequence in mysql's source.
> Uh oh. I'm a little worried about writing tests based on GPLed code
> for Slony-I or other replication systems. Might the
On Fri, Jun 30, 2006 at 01:41:53PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Fri, Jun 30, 2006 at 11:39:04AM -0400, Tom Lane wrote:
> >> It might be worth pointing out that mysql's replication falls
> >> over if you so much as look at it crosseyed. I have not had to
David Fetter <[EMAIL PROTECTED]> writes:
> On Fri, Jun 30, 2006 at 11:39:04AM -0400, Tom Lane wrote:
>> It might be worth pointing out that mysql's replication falls over
>> if you so much as look at it crosseyed. I have not had to use it
>> for production purposes, but I can tell you that the mys
On Fri, Jun 30, 2006 at 11:39:04AM -0400, Tom Lane wrote:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
> > On Fri, 2006-06-30 at 08:17, Jason McManus wrote:
> >> * Replication support still rudimentary.
>
> It might be worth pointing out that mysql's replication falls over
> if you so much as look
On Fri, Jun 30, 2006 at 04:22:28PM +0100, Dave Page wrote:
>
>
> > > * Replication support still rudimentary.
> >
> > H. I think that's an overly simplistic evaluation. The slony
> > replication engine is actually VERY advanced, but the
> > administrative tools consist mostly of "your bra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
paul rivers wrote:
> Out of curiosity, which "big, expensive enterprise database" are
> you spoiled by? Many that I support do not allow DDL within an
> transaction, or if they allow it, there are many caveats and
> rules.
Oracle Rdb. Built by DEC ba
Ron Johnson <[EMAIL PROTECTED]> writes:
> Scott Marlowe wrote:
>> However, the more interesting thing here, is that every
>> statement, including DDL is transactable, except for a couple of
>> big odd ones, like create database. So, in postgresql, you can do:
> But isn't that what it means to be "
alf Of Ron Johnson
Sent: Friday, June 30, 2006 8:22 AM
To: pgsql general
Subject: Re: [GENERAL] Notes on converting from MySQL 5.0.x to PostgreSQL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Marlowe wrote:
[snip]
> However, the more interesting thing here, is that every
> statement,
On Friday 30. June 2006 17:12, Scott Marlowe wrote:
>And, I hate the fact that CTRL-C in the mysql command line tool exits
>the tool instead of interrupting the current query.
I agree, it's a nuisance.
>In PostgreSQL it
>interrupts the current query. CTRL-\ will kill the client if you need
>
Scott Marlowe <[EMAIL PROTECTED]> writes:
> On Fri, 2006-06-30 at 08:17, Jason McManus wrote:
>> * Replication support still rudimentary.
> H. I think that's an overly simplistic evaluation. The slony
> replication engine is actually VERY advanced, but the administrative
> tools consist most
Ron Johnson wrote:
begin;
create table xyz...
alter table abc...
insert into abc select * from iii
update iii...;
drop table iii;
(oops, I messed up something)
rollback;
But isn't that what it means to be "transactional"? Or am I spoiled
by my "big, expensive enterprise database"?
Well, ac
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Scott Marlowe
> Sent: 30 June 2006 16:12
> To: Jason McManus
> Cc: pgsql general
> Subject: Re: [GENERAL] Notes on converting from MySQL 5.0.x
> to PostgreSQL
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Marlowe wrote:
[snip]
> However, the more interesting thing here, is that every
> statement, including DDL is transactable, except for a couple of
> big odd ones, like create database. So, in postgresql, you can do:
>
> begin;
> create table xyz
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: 30 June 2006 15:47
> To: Jason McManus
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Notes on converting from MySQL 5.0.x
> to PostgreSQL 8.
I agree with Tom, nice notes. I noted a few minor issues that seem to
derive from a familiarity with MySQL. I'll put my corrections below...
On Fri, 2006-06-30 at 08:17, Jason McManus wrote:
> On Converting from MySQL 5.0.x to PostgreSQL 8.1.x
> --
"Jason McManus" <[EMAIL PROTECTED]> writes:
>> Perhaps they should go on the project website somewhere?
> I was thinking so as well, but I'm not sure where, or who to submit to
> if there is no wiki or other external editing method. Any pointers
> for who to contact/where to submit?
Not my depar
Gborg http://gborg.postgresql.org/
Greetings,
-Franz
-Ursprüngliche Nachricht-
Von: Tom Lane [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 30. Juni 2006 16:17
An: Jason McManus
Cc: pgsql-general@postgresql.org
Betreff: Re: [GENERAL] Notes on converting from MySQL 5.0.x to PostgreSQL
8.1.
I don't believe there is any fixed "default character set". Each
installation will have a default locale and encoding, but these depend
on the locale under which initdb was run. From the above comment I
surmise that you initdb'd under some UTF8-using locale ...
Ah, great. Thank you for the cl
"Jason McManus" <[EMAIL PROTECTED]> writes:
> I am in the process of converting a couple of major sites from MySQL 5.0.22
> to PostgreSQL 8.1.4, and I thought I would share some of my observations on
> this process and the two database systems in general.
Nice notes! I see only one small error:
On Converting from MySQL 5.0.x to PostgreSQL 8.1.x
--
I am in the process of converting a couple of major sites from MySQL 5.0.22
to PostgreSQL 8.1.4, and I thought I would share some of my observations on
this process and the two database systems i
39 matches
Mail list logo
