<div dir="ltr">Thanks, Pablo!<div><br></div><div>Good to know PostgreSQL support partitions natively. The only drawback - it seems that spreading those partitions across few nodes is still not possible.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 8, 2016 at 5:01 PM, Pablo Sanchez <span dir="ltr"><<a href="mailto:pablo@blueoakdb.com" target="_blank">pablo@blueoakdb.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[ Comments below, in-line ]<br>
<br>
<br>
On 01/08/2016 09:36 AM, Pavels Gurskis wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
</blockquote>
<br>
Hi Paul,<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[ Inquiry about data partitioning ]<br>
</blockquote>
<br>
IMO, where pgpool-II really shines is being able to distribute<br>
read-only queries across a Streaming Replication set up. For example,<br>
A Master database, using synchronous Streaming Replication to keep a<br>
Slave up to date. I'm not sure how you plan on leveraging pgpool-II.<br>
<br>
For example, let's say you have a single PG Instance. Initially<br>
you'll set up the DB server with fast and slow storage. You'll create<br>
your partitions on the respective storage.<br>
<br>
Next, you'll populate the data. Supposing you have three months<br>
total, your initial partition definitions will place the data in the<br>
respective partitions: slow vs fast storage.<br>
<br>
After one month, you'll want to manually move the previous month over<br>
to the slower storage and place new data into the fast storage.<br>
<br>
I think the above handles what you want to do. But only with a single<br>
PG Instance.<br>
<br>
If you set up synchronous Streaming Replication, you'll need to<br>
replicate the above in the Slave. Once done, I think it'd be worth<br>
introducing pgpool-II to Load Balance read-only queries.<br>
<br>
In short, I don't think you need Parallel Query and/or pgpool-II's<br>
data partitioning capabilities. :) But perhaps I'm wrong.<br>
<br>
Anyway, the above are my thoughts .... a bit of a brainstorming.<br>
--<br>
Pablo Sanchez - Blueoak Database Engineering, Inc<br>
Ph: <a href="tel:819.459.1926" value="+18194591926" target="_blank">819.459.1926</a> Blog: <a href="http://pablo-blog.blueoakdb.com" rel="noreferrer" target="_blank">http://pablo-blog.blueoakdb.com</a><br>
iNum: 883.5100.0990.1054<br>
<br>
_______________________________________________<br>
pgpool-general mailing list<br>
<a href="mailto:pgpool-general@pgpool.net" target="_blank">pgpool-general@pgpool.net</a><br>
<a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" rel="noreferrer" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
</blockquote></div><br></div>