On Thu, 27 Jan 2005 00:02:29 -0800, Dustin Sallings <dustin@spy.net> wrote:
> 
> On Jan 26, 2005, at 10:27, Van Ingen, Lane wrote:
> 
> > Clarification: I am talking about SQL coding practices in Postgres
> > (how to write queries for best
> > results), not  tuning-related considerations (although that would be
> > welcomed too).
> 
>         Your question is a bit too vague.  At this point in your development,
> all that really can be said is to understand relational database
> concepts in general, and use explain a lot when developing queries.
> (Oh, and don't forget to analyze before asking specific questions).

I disagree - there are plenty of tricks that are PostgreSQL only, and
many people on this list have that knowledge but it is not documented
anywhere, or is hidden within thousands of mailing list posts.

For example, IIRC when joining an integer column with a SERIAL column,
you must expicitly cast it as an integer or the planner will not use
the indexes, right? (This is a guess, as I remember reading something
like this and thinking, "How in the world is someone supposed to
figure that out, even with EXPLAIN?")

There is another thread about how a query using a WHERE NOT NULL
clause is faster than one without.

These things are PostgreSQL specific, and documenting them would go a
long way towards educating the switchover crowd.

The closest thing I have seen to this is the PostgreSQL Gotchas page:

http://sql-info.de/postgresql/postgres-gotchas.html

HTH,

-- Mitch

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to