agora inbox for pgsql-hackers@postgresql.org
help / color / mirror / Atom feedFrom: Heikki Linnakangas <hlinnakangas@vmware.com>
To: Fujii Masao <masao.fujii@gmail.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: posix_fadvise() and pg_receivexlog
Date: Wed, 6 Aug 2014 21:59:31 +0300
Message-ID: <53E27B13.50506@vmware.com> (raw)
In-Reply-To: <CAHGQGwF4fG8mRB_Ly6toVgVnhNVx+dzsuDyk_j7sPUrLge5k_g@mail.gmail.com>
References: <CAHGQGwF4fG8mRB_Ly6toVgVnhNVx+dzsuDyk_j7sPUrLge5k_g@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 08/06/2014 08:39 PM, Fujii Masao wrote:
> Hi,
>
> The WAL files that pg_receivexlog writes will not be re-read soon basically,
> so we can advise the OS to release any cached pages when WAL file is
> closed. I feel inclined to change pg_receivexlog that way. Thought?
-1. The OS should be smart enough to not thrash the cache by files that
are written sequentially and never read. If we go down this path, we'd
need to sprinkle posix_fadvises into many, many places.
Anyway, who are we to say that they won't be re-read soon? You might e.g
have a secondary backup site where you copy the files received by
pg_receivexlog, as soon as they're completed.
- Heikki
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
view thread (610+ messages) latest in thread
Message-ID: <53E27B13.50506@vmware.com>
Permalink: ../53E27B13.50506@vmware.com/
Also on: postgresql.org/message-id/53E27B13.50506@vmware.com
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-hackers@postgresql.org
Cc: hlinnakangas@vmware.com, masao.fujii@gmail.com
Subject: Re: posix_fadvise() and pg_receivexlog
In-Reply-To: <53E27B13.50506@vmware.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox