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).
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Van Ingen, Lane
Sent: Wed 1/26/2005 11:44 AM
To: pgsql-performance@postgresql.org
Cc:
Subject: [PERFORM] SQL Performance Guidelines
Does anybody know where I can lay my hands on some guidelines to get best SQL performance
out of PostgreSQL? We are about to get into a project that will be new from the ground up (and\we are using Postgres for the first time). Would like to share some guidelines with developers on best practices
in Postgres? Thanks for your help.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
-- SPY My girlfriend asked me which one I like better. pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net> | Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE L_______________________ I hope the answer won't upset her. ____________
---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
