Re: Replication questions - read-only and temporary read/write slaves - Mailing list pgsql-general

From Magnus Hagander
Subject Re: Replication questions - read-only and temporary read/write slaves
Date
Msg-id CABUevEwnjBCkcuSPJrt3YNyfZJo_2KKzC2+uUNKN0qGqSi_t4w@mail.gmail.com
Whole thread Raw
In response to Replication questions - read-only and temporary read/write slaves  (Tiffany Thang <tiffanythang@gmail.com>)
Responses Re: Replication questions - read-only and temporary read/write slaves
List pgsql-general
On Fri, Dec 15, 2017 at 6:03 PM, Tiffany Thang <tiffanythang@gmail.com> wrote:
Hi,
In PostgreSQL, would it be possible to

1. set up a read-only slave database? The closest solution I could find is Hot Standby but the slave would not be accessible until after a failover.

Hot Standby will give you a standby database that is accessible, but in read-only mode. This sounds like what you're looking for.

 
2. temporary convert a read-only slave in read-write mode for testing read/write workloads? Currently in Oracle, we can temporary open our read-only standby database in read-write mode to occasionally test our read-write workloads. We would stop the log apply on the standby database, convert the read-only database to read-write,
perform our read/write test, discard all the changes after testing and reopen and resync the standby database in read-only mode. Is there a similar feature in PostgreSQL or are there ways to achieve something close to our needs?

No, you can't do this with postgres natively.

You could snapshot your filesystem before opening it and then roll back to that snapshot, or something like that, but you cannot do it with just PostgreSQL functionality.
 
--

pgsql-general by date:

Previous
From: Tiffany Thang
Date:
Subject: Replication questions - read-only and temporary read/write slaves
Next
From: Tiffany Thang
Date:
Subject: Re: Replication questions - read-only and temporary read/write slaves