pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Christopher Kings-Lynne <chris.kings-lynne@calorieking.com>
To: David Wheeler <david@kineticode.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: IMMUTABLE?
Date: Wed, 17 May 2006 09:29:13 +0800
Message-ID: <446A7C69.5030905@calorieking.com> (raw)
In-Reply-To: <719F1E6C-4695-4FD2-A73B-0E3AE173B8F0@kineticode.com>
References: <2D4C0FA5-DB75-45EA-91D2-7B4F6DD55083@kineticode.com>
	<5211.1147749711@sss.pgh.pa.us>
	<3F0CF576-8C6F-433C-9942-BB36F4E1A194@kineticode.com>
	<5894.1147753901@sss.pgh.pa.us>
	<719F1E6C-4695-4FD2-A73B-0E3AE173B8F0@kineticode.com>

> Yes, but there are definitely programming cases where 
> memoization/caching definitely helps. And it's easy to tell for a given 
> function whether or not it really helps by simply trying it with CACHED 
> and without.
> 
> Would this be a simple thing to implement?

It's called a "table" :)

view thread (11+ messages)  latest in thread

Message-ID: <446A7C69.5030905@calorieking.com>
Permalink:  ../446A7C69.5030905@calorieking.com/
Also on:    postgresql.org/message-id/446A7C69.5030905@calorieking.com

copy link · copy postgr.es

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: chris.kings-lynne@calorieking.com, david@kineticode.com, tgl@sss.pgh.pa.us
  Subject: Re: IMMUTABLE?
  In-Reply-To: <446A7C69.5030905@calorieking.com>

* 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