From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Keaton Adams <kadams(at)mxlogic(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Persistent objects within PG or the availability of non-logged tables or databases? |
Date: | 2008-04-08 17:27:11 |
Message-ID: | 20080408102711.377d7c29@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 8 Apr 2008 11:19:57 -0600
Keaton Adams <kadams(at)mxlogic(dot)com> wrote:
> there a way for an object (variable/table/etc) to remain persistent
> in memory that is shared among multiple client sessions? If not, an
> alternative we thought of is to use a small table within the DB in
> conjunction with a function to keep track of the last set of data.
> The question we have, though, is the rate at which the table is
> updated (possibly many times per second) and the amount of WAL data
> that is generated by this operation.
You could use pg_memcache.
>
> Is there such as thing as a non-logged table or a non-logged database
> in PG?
No but if the updates taking place are on columns that are not indexed
(and you are running 8.3) then HOT will kick in and the load is
significantly reduced.
E.g.; CREATE TABLE foo (id serial pk, bar text);
UPDATE foo SET bar = 'baz';
Will not create a dead row and thus greatly reduces overall load and
maintenance requirements.
SIncerely,
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Mikko Partio | 2008-04-08 17:49:47 | Re: "too many trigger records found for relation xyz" |
Previous Message | Tony Caduto | 2008-04-08 17:21:56 | Re: Number or parameters for functions - limited to 32 ? |