From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | suchindra(at)linuxlabs(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Question for the developers. |
Date: | 2003-11-10 15:57:14 |
Message-ID: | 3FAFB55A.2020501@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
suchindra(at)linuxlabs(dot)com wrote:
> Hi,
>
> I am Suchindra Katageri and am working as a Software Engineer at
> Linuxlabs, Atlanta, GA.
>
> I am presently working on developing libraries to make postgresql
> run on a cluster. I was wondering if it was possible to force Database
> writes to stable storage, without messing up with the postgres code.
> e.g. force the PostgreSQL to write to stable storage after an INSERT
> command.
I don't see how that would help you very far.
PostgreSQL holds disk buffers in a shared memory cache. And unless you
modify that cache, it would not read from the file again if it thinks it
knows the content already. How do you intend to remove pages from that
shared buffer cache at the time, another cluster member modifies the
same logical page?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2003-11-10 16:02:32 | Re: [HACKERS] BEGIN vs START TRANSACTION |
Previous Message | Tom Lane | 2003-11-10 15:54:53 | Re: Experimental patch for inter-page delay in VACUUM |