Re: Why frequently updated tables are an issue

From: Manfred Spraul <manfred(at)colorfullife(dot)com>
To: pgsql(at)mohawksoft(dot)com
Cc: Christopher Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Why frequently updated tables are an issue
Date: 2004-10-20 17:10:35
Message-ID: 41769C0B.7060004@colorfullife.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

pgsql(at)mohawksoft(dot)com wrote a few months ago:

>PostgreSQL's behavior on these cases is poor. I don't think anyone who has
>tried to use PG for this sort of thing will disagree, and yes it is
>getting better. Does anyone else consider this to be a problem? If so, I'm
>open for suggestions on what can be done. I've suggested a number of
>things, and admittedly they have all been pretty weak ideas, but they were
>potentially workable.
>
>
>
What about a dblink style interface to a non-MVCC SQL database?
I think someone on this list mentioned that there are open source
in-memory SQL databases.

--
Manfred

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Darcy Buskermolen 2004-10-20 17:26:07 -HEAD contrib/dblink regress failure on SPARC/Solaris 8
Previous Message PostgreSQL Bugs List 2004-10-20 17:01:37 BUG #1290: Default value and ALTER...TYPE