Date: Wed, 28 May 2003 21:28:15 +1000
From: Peter Lavender <plaven@bigpond.net.au>
To: pgsql-sql@postgresql.org, pgsql-performance@postgresql.org
Message-ID: <20030528112815.GD816@piglet2>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i

pgsql-bugs@postgresql.org
Cc: 
Bcc: 
Subject: Re: [PERFORM] [SQL] Unanswered Questions WAS: An unresolved performance
Reply-To: plaven@bigpond.net.au
In-Reply-To: <Pine.LNX.4.33.0305081019300.11328-100000@css120.ihs.com>
X-Operating-System: Linux/2.4.18-686-smp (i686)
X-Uptime:  21:03:03 up 8 days, 22:55,  8 users,  load average: 1.00, 1.00, 1.00

* scott.marlowe (scott.marlowe@ihs.com) wrote:


> On Thu, 8 May 2003, johnnnnnn wrote:
> 
> > > I hate to point this out, but "TIP 4" is getting a bit old and the 6
> 
> Also, some tips might well cross over, like say, vacuum and analyze 
> regularly.  Hmmm.  Sounds like a job for a relational database :-)

Did this get carried any further?

I'd love to see something come out of it.  But I'd really like to see more
of the kind of tricks and tips, like how to dump all databases using a
script of 3 lines(?) I'm sure I've seen it before.  The extra lines I
don't think would be a major pain given the added value.

Even if it's too much, how about somewhere on techdocs for the script and
a link in the tips 'n tricks line?


Pete
:wq