Thanks for the information and the URLs!
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Streaming-Replication-Error-on-Standby-tp5791463p5791588.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql
On 02/11/2014 10:12 AM, bobJobS wrote:
Postgres 9.3.2.
RHEL 5
After performing all of the Streaming Replication setup steps, I get the
following error message in my standby DB log file.
database system identifier differ between the primary and standby
I've double checked the recovery.conf f
On 02/11/2014 10:12 AM, bobJobS wrote:
Postgres 9.3.2.
RHEL 5
After performing all of the Streaming Replication setup steps, I get the
following error message in my standby DB log file.
database system identifier differ between the primary and standby
I've double checked the recovery.conf f
On Tue, Feb 11, 2014 at 11:25 AM, bobJobS wrote:
>
> To get the standby server to a point, I tool a globals dump and a data dump
> of the primary server and build the standby.
>
> Then I executed pg_startbackup, rsync data dir to standby data dir (to
> catch
> any changes made while I was buildin
To get the standby server to a point, I tool a globals dump and a data dump
of the primary server and build the standby.
Then I executed pg_startbackup, rsync data dir to standby data dir (to catch
any changes made while I was building the standby) and finally
pg_stopbackup... all on the primary
On Tue, Feb 11, 2014 at 10:12 AM, bobJobS wrote:
> Postgres 9.3.2.
> RHEL 5
>
> After performing all of the Streaming Replication setup steps,
>
What replication steps?
> database system identifier differ between the primary and standby
>
How did you take the initial backup of the master? D
Postgres 9.3.2.
RHEL 5
After performing all of the Streaming Replication setup steps, I get the
following error message in my standby DB log file.
database system identifier differ between the primary and standby
I've double checked the recovery.conf file and it contains the correct
hostname,
PostgreSQL 9.2 on Windows Server 2008 R2 64-bit
Streaming Replication initialised & working on a 500GB database.
Following day on slave, following errors in the log:
2012-11-27 09:57:53 GMT WARNING: page 911726 of relation
pg_tblspc/16570/PG_9.2_201204301/16571/16595 is uninitialized
2012-11-27
On Mon, 2012-04-30 at 17:23 -0400, Andrew Hannon wrote:
> 1. Is our data intact? PG eventually starts up, and it seems like once
> the streaming suffers the FATAL error, it falls back to performing log
> restores.
I don't see anything alarming there. Postgres will not start up if it
thinks it's r
Hello,
We were auditing our logs on one of our PG 9.0.6 standby servers that we use
for nightly snapshotting. The high-level process is:
1. Stop PG
2. Snapshot
3. Start PG
Where "Snapshot" includes several steps to ensure data/filesystem integrity.
The archive command on the master continues t
10 matches
Mail list logo
