[prev in list] [next in list] [prev in thread] [next in thread]
List: postgresql-general
Subject: Re: [HACKERS] Why frequently updated tables are an issue
From: David Fetter <david () fetter ! org>
Date: 2004-10-20 19:59:58
Message-ID: 20041020195958.GC31024 () fetter ! org
[Download RAW message or body]
On Wed, Oct 20, 2004 at 07:10:35PM +0200, Manfred Spraul wrote:
> pgsql@mohawksoft.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.
Funny you should mention this. I'm working on a generalized one that
uses PL/PerlU at
http://fetter.org/pg_ps/
Thanks to Josh Berkus for design ideas & implementation roadmap, and
to Josh Drake, Andrew Dunstan, Abhijit Menon-Sen and (of course) Tom
Lane for the infrastructure that makes this doable. :)
Cheers,
D
--
David Fetter david@fetter.org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vote!
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic