From: | François Beausoleil <francois(at)teksol(dot)info> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Allowed DML on replicas? |
Date: | 2012-03-01 13:24:21 |
Message-ID: | 66DA7599A7D84E55BFF37B873AAED576@ftml.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi!
I'm getting ready to build a reporting server, one where long-running queries and backups will be taken from. This new server will be a slave from the master where all changes are done. Some reports are better expressed with extracting a subset of the data and leaving it in a table to be reused, until the report set is done.
In my specific case, I have a table with ~30M rows representing Twitter users. When I JOIN this table with the interactions I have on hand, it takes a long time, because PostgreSQL ends up doing a full table scan of the personas table. To make subsequent reporting steps easier, I do the JOIN only once, and write the results to a table.
My question is:
* Can a new schema be created on a replica?
* Will this impact replication in any way?
* If I can't, what would you advise? dump / reload in a separate database without dropping the table, to keep the extra schemas around?
Thanks!
François Beausoleil
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Mamin | 2012-03-01 13:41:58 | 2 x duplicate key value violation: which exception comes first ? |
Previous Message | Ivan Voras | 2012-03-01 12:33:06 | Re: what Linux to run |