pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PFC <lists@boutiquenumerique.com>
To: Simon Riggs <simon@2ndquadrant.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, "John A Meinel" <john@arbash-meinel.com>
Cc: bizgres-general <bizgres-general@pgfoundry.org>
Cc: Dan Harris <fbsd@drivefaster.net>
Subject: Re: [Bizgres-general] Re: faster INSERT with possible
Date: Wed, 27 Jul 2005 23:53:02 +0200
Message-ID: <op.suldqocith1vuj@localhost> (raw)
In-Reply-To: <1122500267.3670.184.camel@localhost.localdomain>
References: <BF0BDD48.9FFF%llonergan@greenplum.com>
	<200507270929.10251.josh@agliodbs.com>
	<1122500267.3670.184.camel@localhost.localdomain>



> I had in mind the extra tables that an application sometimes needs to
> operate faster. Denormalisations, pre-joined tables, pre-calculated
> results, aggregated data. These are not temporary tables, just part of
> the application - multi-user tables that stay across shutdown/restart.

	You could also add caching search results for easy pagination without  
redoing always entirely on each page the Big Slow Search Query that every  
website has...



view thread (6+ messages)  latest in thread

Message-ID: <op.suldqocith1vuj@localhost>
Permalink:  ../op.suldqocith1vuj@localhost/
Also on:    postgresql.org/message-id/op.suldqocith1vuj@localhost

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: lists@boutiquenumerique.com, simon@2ndquadrant.com, josh@agliodbs.com, john@arbash-meinel.com, bizgres-general@pgfoundry.org, fbsd@drivefaster.net
  Subject: Re: [Bizgres-general] Re: faster INSERT with possible
  In-Reply-To: <op.suldqocith1vuj@localhost>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox