Re: Configuring Standby Server in PostgreSQL 9.3.3 - Mailing list pgsql-bugs

From
Subject Re: Configuring Standby Server in PostgreSQL 9.3.3
Date
Msg-id 20140404074954.5a830134ae84016b0174832fdc1a3173.85ff9d3a15.wbe@email11.secureserver.net
Whole thread Raw
In response to Configuring Standby Server in PostgreSQL 9.3.3  (<fburgess@radiantblue.com>)
List pgsql-bugs
<span style=3D"font-family:Verdana; color:#000000; font-size:10=
pt;">No, Haven't set the server as primary yet. Spent yesterday instal=
ling PostgreSQL 9.3.3 and PostGIS 2.1.1 on the standby server. Now that's d=
one, I think the next step is to run a backup from the yet to be setup Prim=
ary server.=0A<blockquote id=3D"replyBlockquote" webmail=3D"1=
" style=3D"border-left: 2px solid blue; margin-left: 8px; padding-left: 8px=
; font-size:10pt; color:black; font-family:verdana;">=0A<div id=3D"wmQuoteW=
rapper">=0A-------- Original Message --------=0ASubject: Re: [BUGS] Con=
figuring Standby Server in PostgreSQL 9.3.3=0AFrom: chileme88 <<a hr=
ef=3D"mailto:michele.mariani@databtech.com">michele.mariani@databtech.com</=
a>>=0ADate: Thu, April 03, 2014 8:31 am=0ATo: <a href=3D"mailto:=
pgsql-bugs@postgresql.org">pgsql-bugs@postgresql.org=0A=0Ahave =
u already edit postgres.conf on primary?=0A=0A=0A=0A-----<b=
r>=0AMichele Mariani=0ADatabase & Technology s.r.l. =0Atel: +39=
 02 89500080=0A--=0AView this message in context: <a href=3D"http:/=
/postgresql.1045698.n5.nabble.com/Configuring-Standby-Server-in-PostgreSQL-=
9-3-3-tp5798372p5798529.html">http://postgresql.1045698.n5.nabble.com/Confi=
guring-Standby-Server-in-PostgreSQL-9-3-3-tp5798372p5798529.html=0A=
Sent from the PostgreSQL - bugs mailing list archive at <a href=3D"http://N=
abble.com">Nabble.com.=0A=0A=0A-- =0ASent via pgsql-bug=
s mailing list (pgsql-bugs@pos=
tgresql.org)=0ATo make changes to your subscription:=0A<a href=
=3D"http://www.postgresql.org/mailpref/pgsql-bugs">http://www.postgresql.or=
g/mailpref/pgsql-bugs=0A=0A=0A</ht=
ml>

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #9849: walreceiver's DEBUG message reports wrong timestamp
Next
From: Shahar
Date:
Subject: Re: BUG #9833: daterange is not utilizing index correctly