MIME-Version: 1.0
In-Reply-To: <fe49c502-2946-91a2-e921-72a62d2ee854@evolu-s.it>
References: 
 <CAAMgDXkDgmnnzdDtk1pOX473eLK=eQN+MnccncGHiNBAtiRnTw@mail.gmail.com>
 <fe49c502-2946-91a2-e921-72a62d2ee854@evolu-s.it>
From: Soni M <diptatapa@gmail.com>
Date: Sun, 10 Sep 2017 12:49:41 +0700
Message-ID: 
 <CAAMgDXnvp6VvU6ZVBZwvrhub-C3nF6tbriiGjtj6W5a+C_19Yg@mail.gmail.com>
Subject: Re: [SPAM] OS cache management
To: Moreno Andreo <moreno.andreo@evolu-s.it>
Cc: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Content-Type: multipart/alternative; boundary="001a113f92ae6420cf0558cf60e4"
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

--001a113f92ae6420cf0558cf60e4
Content-Type: text/plain; charset="UTF-8"

Yeah, thanks. We have it in count.

On Wed, Sep 6, 2017 at 9:45 PM, Moreno Andreo <moreno.andreo@evolu-s.it>
wrote:

> Il 06/09/2017 10:12, Soni M ha scritto:
>
>>
>>
>> Let's say I have 10 year data, and commonly used data only the last 1
>> year. This data is quite big, so each table and index file is divided into
>> several file in PGDATA/base
>>
>> May not be relevant to what you asked, but if you want to keep last yeat
> data in a "small and fast" dataset separated (physically separated!) by old
> data (that's still available, but response times may vary), IMHO you should
> consider partitioning...
> https://www.postgresql.org/docs/current/static/ddl-partitioning.html
>
> HTH,
> Moreno.-
>
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>


-- 
Regards,

Soni Maula Harriz

--001a113f92ae6420cf0558cf60e4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yeah, thanks. We have it in count.</div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Wed, Sep 6, 2017 at 9:45 PM, Mor=
eno Andreo <span dir=3D"ltr">&lt;<a href=3D"mailto:moreno.andreo@evolu-s.it=
" target=3D"_blank">moreno.andreo@evolu-s.it</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><span class=3D"">Il 06/09/2017 10:12, Soni M ha s=
critto:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
Let&#39;s say I have 10 year data, and commonly used data only the last 1 y=
ear. This data is quite big, so each table and index file is divided into s=
everal file in PGDATA/base<br>
<br>
</blockquote></span>
May not be relevant to what you asked, but if you want to keep last yeat da=
ta in a &quot;small and fast&quot; dataset separated (physically separated!=
) by old data (that&#39;s still available, but response times may vary), IM=
HO you should consider partitioning...<br>
<a href=3D"https://www.postgresql.org/docs/current/static/ddl-partitioning.=
html" rel=3D"noreferrer" target=3D"_blank">https://www.postgresql.org/doc<w=
br>s/current/static/ddl-partition<wbr>ing.html</a><br>
<br>
HTH,<br>
Moreno.-<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
<br>
<br>
-- <br>
Sent via pgsql-performance mailing list (<a href=3D"mailto:pgsql-performanc=
e@postgresql.org" target=3D"_blank">pgsql-performance@postgresql.<wbr>org</=
a>)<br>
To make changes to your subscription:<br>
<a href=3D"http://www.postgresql.org/mailpref/pgsql-performance" rel=3D"nor=
eferrer" target=3D"_blank">http://www.postgresql.org/mail<wbr>pref/pgsql-pe=
rformance</a><br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r><div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div di=
r=3D"ltr"><div>Regards,</div><div><br></div>Soni Maula Harriz</div></div>
</div>

--001a113f92ae6420cf0558cf60e4--