My guess is this will happen natually after using postgres for a short time.
(That's what happened to me.)
----- Original Message -----
From: "Alvaro Herrera" <[EMAIL PROTECTED]>
To: "scott.marlowe" <[EMAIL PROTECTED]>
Cc: "Errol Neal" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 15, 2003 1:04 PM
Subject: Re: [GENERAL] Porting Code to Postgresql
> On Wed, Oct 15, 2003 at 12:44:55PM -0600, scott.marlowe wrote:
>
> > All the rest if pretty straight forward hacking, having converted or
> > helped to convert a few other MySQL tools to Postgresql recently.
>
> Of course, to get maximum performance you should drop the MySQL support
> and instead of coding workarounds for missing functionality, use
> whatever Postgres gives you (which is much more than what MySQL gives
> you).
>
> --
> Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
> "Si quieres ser creativo, aprende el arte de perder el tiempo"
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
