meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 4 months |
| seen | Jan 22 at 5:56 | |
| stats | profile views | 19 |
|
Dec 4 |
accepted | Is it a good idea to move high-volume and highly-accessed tables to a separate database? |
|
Dec 4 |
accepted | Database archive solutions |
|
Nov 16 |
comment |
Database archive solutions I also read about PostgreSQL inheritance. Can you clarify this - Why public.posts should inherit from posts_all while posts_all itself is created as a table using (LIKE public.posts)? |
|
Nov 15 |
comment |
Database archive solutions So in this case, which table will be normally empty ( posts, posts-all or posts-archive), that exists just to represent the entire data set? |
|
Nov 15 |
comment |
Database archive solutions In real-time application, there will be more than one dependent/child tables connected/related to with the parent/master table. So the steps outlined here is automatically applicable to all its dependent/child tables as well? Is my understanding correct? |
|
Nov 15 |
comment |
Database archive solutions Thanks for the edit. I'll go thro' it again. |
|
Nov 15 |
comment |
Database archive solutions I couldn't able to clearly understand the 2nd step Create tables (table posts example):. Can you explain that specific step on how many tables are there in total and how the inheritance between tables are related to each other? |
|
Nov 14 |
asked | Database archive solutions |
|
Sep 27 |
awarded | Popular Question |
|
Sep 26 |
comment |
Is it a good idea to move high-volume and highly-accessed tables to a separate database? @FrankHeikens: What is your RAM size? |
|
Sep 26 |
comment |
Is it a good idea to move high-volume and highly-accessed tables to a separate database? Thanks once again for your inputs. To let you know on the environment setup part, our application is hosted in the Amazon EC2 Cloud environment. |
|
Sep 26 |
awarded | Supporter |
|
Sep 26 |
comment |
Is it a good idea to move high-volume and highly-accessed tables to a separate database? We've 35 GB RAM available in the server. I feel, in my case, there is enough memory available. |
|
Sep 26 |
awarded | Commentator |
|
Sep 26 |
comment |
Is it a good idea to move high-volume and highly-accessed tables to a separate database? Thanks for your suggestion about moving table to a different harddisk to improve I/O performance. At the time of writing this question, when I said, move to a different database, I thought of moving to a separate server itself in my mind. In our current setup, both web server and database share the same server. |
|
Sep 25 |
comment |
Is it a good idea to move high-volume and highly-accessed tables to a separate database? @FrankHeikens: Thanks for your comment with your real-time database size. Would you mind sharing your PostgreSQL configuration ( postgresql.conf)? Can you share any performance tuning tips in this regard? Thanks. |
|
Sep 25 |
asked | Is it a good idea to move high-volume and highly-accessed tables to a separate database? |
|
Feb 15 |
awarded | Yearling |
|
Dec 22 |
awarded | Nice Question |
|
Oct 12 |
accepted | How to upgrade PostgreSQL minor releases without a dump/restore? |
