RE: MySQL -> pgsql - Mailing list pgsql-general

From KuroiNeko
Subject RE: MySQL -> pgsql
Date
Msg-id 39EF69A7.nail7X11G7CX@ed.ed
Whole thread Raw
In response to RE: MySQL -> pgsql  ("Diehl, Jeffrey" <jdiehl@sandia.gov>)
List pgsql-general
> Conversion tools? Na, that's just a small part of what I do.

 Since  it's  a  network  monitor,  chances are  you're  not  using  exotic
datatypes incompatible,  or non-existant in  PGSQL? If so, the  fastest way
would be to get a `dump' schema + data script from MySQL and adjust it with
sed or PERL where it's required.
 On the other hand, just porting the  tables is probably not what you want.
This  will remain  MySQL, only  executed  by PGSQL:  no DRI,  no rules,  no
triggers, nothing. Probably  it's worth designing the  schema from scratch,
using natural features of PGSQL and work out migration procedures then?
 Not knowing exactly what data you operate it's hard to tell more.


--

 Well I tried to be meek
  And I have tried to be mild
 But I spat like a woman
  And I sulked like a child
 I have lived behind the walls
  That have made me alone
 Striven for peace
  Which I never have known

 Dire Straits, Brothers In Arms, The Man's Too Strong (Knopfler)


pgsql-general by date:

Previous
From: DaVinci
Date:
Subject: A stupid question :)
Next
From: Joseph Shraibman
Date:
Subject: Re: Any risk in increasing BLCKSZ to get larger tuples?