Re: Mysql -> Postgresql pitfalls - Mailing list pgsql-docs

From scott.marlowe
Subject Re: Mysql -> Postgresql pitfalls
Date
Msg-id Pine.LNX.4.33.0308011426280.30340-100000@css120.ihs.com
Whole thread Raw
In response to Re: Mysql -> Postgresql pitfalls  ("Chad N. Tindel" <chad@tindel.net>)
Responses Re: Mysql -> Postgresql pitfalls
List pgsql-docs
On Fri, 1 Aug 2003, Chad N. Tindel wrote:

> Excellent!  That is exactly what I'm talking about.
>
> BTW, the "my2pg.pl" link is a dead link.

This is probably something that could be codified a bit here in the news
group.

I'd say the pitfalls I'm aware of are:

autoincrement fields -> sequences
full text indexing -> fts/tsearch etc...
enum -> check constraint
vacuum / analyze
simple performance tuning (out of the box the postgresql.conf settings
aren't really all that great, but they let postgresql come up on almost
anything.)
pg_hba.conf default setting that doesn't allow tcp/ip connections
not being able to run postgresql as root (a good thing TM)


pgsql-docs by date:

Previous
From: "Chad N. Tindel"
Date:
Subject: Re: Mysql -> Postgresql pitfalls
Next
From: "Chad N. Tindel"
Date:
Subject: Re: Mysql -> Postgresql pitfalls