From rwelty@ltionline.com Mon Apr 2 21:20:57 2012 Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 8279D1782AF7 for ; Mon, 2 Apr 2012 18:20:57 -0300 (ADT) Received: from 66-109-41-228.tvc-ip.com ([66.109.41.228] helo=mx1-sch.ltionline.com) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SEogK-0008Lv-7I for pgsql-general@postgresql.org; Mon, 02 Apr 2012 21:20:56 +0000 X-ASG-Debug-ID: 1333401641-722d000c0000-zW6XKP X-Barracuda-URL: http://10.1.1.20:8000/cgi-bin/mark.cgi Received: from ltischx01.lti.int (localhost [127.0.0.1]) by mx1-sch.ltionline.com (Spam Firewall) with ESMTP id AC6AB397E58 for ; Mon, 2 Apr 2012 17:20:41 -0400 (EDT) Received: from ltischx01.lti.int ([192.168.161.15]) by mx1-sch.ltionline.com with ESMTP id ySM7Mja3rhratUuJ for ; Mon, 02 Apr 2012 17:20:41 -0400 (EDT) X-Barracuda-Envelope-From: rwelty@ltionline.com X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD1116.87A7FC50" X-ASG-Orig-Subj: 9.1.3: launching streaming replication Subject: 9.1.3: launching streaming replication Date: Mon, 2 Apr 2012 17:21:12 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 9.1.3: launching streaming replication Thread-Index: Ac0RFoeNnJ970jf0QEKev1MLNIX2Xg== From: "Welty, Richard" To: X-Barracuda-Connect: UNKNOWN[192.168.161.15] X-Barracuda-Start-Time: 1333401641 X-Barracuda-Virus-Scanned: by Barracuda Spam & Virus Firewall at ltionline.com X-Pg-Spam-Score: -0.9 (/) X-Archive-Number: 201204/34 X-Sequence-Number: 186347 This is a multi-part message in MIME format. ------_=_NextPart_001_01CD1116.87A7FC50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable i have a server in the ec2 cloud which in theory is set up as a master; = it starts and runs. i've got an amazon s3 bucket mounted using s3fs on = both the master and the standby (the standby is also set up in the ec2 = cloud.) i followed the steps here: = http://wiki.postgresql.org/wiki/Streaming_Replication and have the backup and the wal archive on the s3 bucket and they are = both there. when i go to start the hot standby, i pretty consistently get LOG: entering standby mode cp: cannot stat `/db-backup/wal_archive/000000010000000000000001': No = such file or directory WARNING: WAL was generated with wal_level=3Dminimal, data may be = missing HINT: This happens if you temporarily set wal_level=3Dminimal without = taking a new base backup. FATAL: hot standby is not possible because wal_level was not set to = "hot_standby" on the master server HINT: Either set wal_level to "hot_standby" on the master, or turn off = hot_standby here. LOG: startup process (PID 29938) exited with exit code 1 LOG: aborting startup due to startup process failure and the startup of the hot standby fails. the Riggs admin cookbook says = "you will need a short delay", but has no guesstimate on the length = required. i don't even know if i'm seeing this problem or something = else. if i need to run a new backup, what cleanup do i need to do of old = backups and wal_archives? could this be interfering with the startup of = the standby? i've gone through several iterations and fixed some = problems, and wonder if there's obsolete data that is messing things up? thanks, richard ------_=_NextPart_001_01CD1116.87A7FC50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 9.1.3: launching streaming replication

i have a server in the ec2 cloud which in theory is = set up as a master; it starts and runs. i've got an amazon s3 bucket = mounted using s3fs on both the master and the standby (the standby is = also set up in the ec2 cloud.)

i followed the steps here: http://wik= i.postgresql.org/wiki/Streaming_Replication
and have the backup and the wal archive on the s3 bucket and they are = both there.

when i go to start the hot standby, i pretty consistently get


LOG:  entering standby mode
cp: cannot stat `/db-backup/wal_archive/000000010000000000000001': No = such file or directory
WARNING:  WAL was generated with wal_level=3Dminimal, data may be = missing
HINT:  This happens if you temporarily set wal_level=3Dminimal = without taking a new base backup.
FATAL:  hot standby is not possible because wal_level was not set = to "hot_standby" on the master server
HINT:  Either set wal_level to "hot_standby" on the = master, or turn off hot_standby here.
LOG:  startup process (PID 29938) exited with exit code 1
LOG:  aborting startup due to startup process failure


and the startup of the hot standby fails. the Riggs admin cookbook says = "you will need a short delay", but has no guesstimate on the = length required. i don't even know if i'm seeing this problem or = something else.

if i need to run a new backup, what cleanup do i need to do of old = backups and wal_archives? could this be interfering with the startup of = the standby? i've gone through several iterations and fixed some = problems, and wonder if there's obsolete data that is messing things = up?

thanks,
   richard

------_=_NextPart_001_01CD1116.87A7FC50-- From htfoot@gmail.com Mon Apr 2 23:19:59 2012 Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 709FF1782AF9 for ; Mon, 2 Apr 2012 20:19:59 -0300 (ADT) Received: from mail-vb0-f46.google.com ([209.85.212.46]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SEqXP-0000mh-KN for pgsql-general@postgresql.org; Mon, 02 Apr 2012 23:19:58 +0000 Received: by vbbff1 with SMTP id ff1so2022796vbb.19 for ; Mon, 02 Apr 2012 16:19:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UTbhHg82QV9WzQu0is6PoJaDkvyPWEa/s/beLMxNIIk=; b=vcphZExFkIxYcuRRVTge5pc8OBHi8lsD7thk/Pr3smscU081ZFHQbpfOwy7jhLc+24 kmf12h1RB7hZFsmGzZvhwukn2h23enPKB13ykTUOl+ANFzJWEY6PseCb26svBor4GQ26 NWOt2tEa04yiHoK4npP4CDB7f0YdoJ93yd0b1FT/5m+htxyEv4r8AUp8IFd33cF67k5q s5B3rCfVcsyNpJlM0/BY6CbbbZ3eCusObyyyIB7vQwicCwxMFrD3JWS4WDZ0ntAO4plq +hT9NGLhcitf4f5GkZGxcXnpKd/k+GDqyrVYnTNOMyiH/PHuPPLYanTK2KCTsKXrF3Ac GpeA== MIME-Version: 1.0 Received: by 10.52.67.11 with SMTP id j11mr4023684vdt.40.1333408778246; Mon, 02 Apr 2012 16:19:38 -0700 (PDT) Received: by 10.220.189.201 with HTTP; Mon, 2 Apr 2012 16:19:38 -0700 (PDT) In-Reply-To: References: Date: Mon, 2 Apr 2012 18:19:38 -0500 Message-ID: Subject: Re: 9.1.3: launching streaming replication From: Michael Nolan To: "Welty, Richard" Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary=20cf307f35929159e204bcba6c34 X-Pg-Spam-Score: -2.7 (--) X-Archive-Number: 201204/38 X-Sequence-Number: 186351 --20cf307f35929159e204bcba6c34 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Apr 2, 2012 at 4:21 PM, Welty, Richard wrote: I got similar messages the first few times I tried to start up my slave server, I never did figure out exactly what caused it. You can either delete all the files on the slave and try again, or do what I did, write a script that handles transferring just the files needed to resync the slave. Here's the script I've been using to transfer the files between my two servers to resync them. This is not a production-ready script. I have a second tablespace, so there are two 'data' transfers plus the xlog transfer. (You may run into issues transferring the pg_tblspc directory, as I did, hence the '-safe-links' parameter.) The '-delete' term deletes any files on the slave that aren't on the server, unless you list them in an '--exclude' clause.) /usr/local/pgsql/bin/psql -c "select pg_start_backup('tardir',true)" postgres postgres rsync -av --exclude log.out --exclude postgresql.conf \ --exclude postgresql.pid --delete --exclude pg_hba.conf \ --exclude pg_xlog --exclude server.crt --exclude server.key \ --exclude restore.conf --exclude restore.done \ --safe-links /usr/local/pgsql/data/ postgres@xxx:/usr/local/pgsql/data rsync -av /usr/local/pgsql/data2/ postgres@xxx:/usr/local/pgsql/data2 /usr/local/pgsql/bin/psql -c "select pg_stop_backup()" postgres postgres rsync -av /usr/local/pgsql/data/pg_xlog postgres@xxx:/usr/local/pgsql/data/ echo "ok to start standby" -- Mike Nolan --20cf307f35929159e204bcba6c34 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, Apr 2, 2012 at 4:21 PM, Welty, R= ichard <rwelty= @ltionline.com> wrote:

I got similar messages the firs= t few times I tried to start up my slave server, I never did figure out exa= ctly what caused it.

You can either delete all the files on the slave and try again, or do w= hat I did, write a script that handles transferring just the files needed t= o resync the slave.

Here's the script I've been using to tr= ansfer the files between my two servers to resync them. This is not a produ= ction-ready script.

I have a second tablespace, so there are two 'data' transfers p= lus the xlog transfer.=A0 (You may run into issues transferring the pg_tbls= pc directory, as I did, hence the '-safe-links' parameter.) The = 9;-delete' term deletes any files on the slave that aren't on the s= erver, unless you list them in an '--exclude' clause.)

/usr/local/pgsql/bin/psql -c "select pg_start_backup('tardir&#= 39;,true)" postgres postgres

rsync -av --exclude log.out --excl= ude postgresql.conf \
--exclude postgresql.pid --delete --exclude pg_hba= .conf \
--exclude pg_xlog --exclude server.crt --exclude server.key \
--exclude = restore.conf --exclude restore.done \
--safe-links /usr/local/pgsql/data= / postgres@xxx:/usr/local/pgsql/data

rsync -av /usr/local/pgsql/data= 2/ postgres@xxx:/usr/local/pgsql/data2

/usr/local/pgsql/bin/psql -c "select pg_stop_backup()" postgr= es postgres

rsync -av /usr/local/pgsql/data/pg_xlog postgres@xxx:/us= r/local/pgsql/data/

echo "ok to start standby"

--
Mike Nolan


--20cf307f35929159e204bcba6c34-- From htfoot@gmail.com Mon Apr 2 23:29:49 2012 Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id A5D111782AF9 for ; Mon, 2 Apr 2012 20:29:49 -0300 (ADT) Received: from mail-vx0-f174.google.com ([209.85.220.174]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SEqh1-00010v-GX for pgsql-general@postgresql.org; Mon, 02 Apr 2012 23:29:48 +0000 Received: by vcqp1 with SMTP id p1so2003631vcq.19 for ; Mon, 02 Apr 2012 16:29:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Xd5YF7vsLyZlLX4OBQ5chOaXTWQnC40tJdFf1cG6s7c=; b=t4muLl9kQ3nc01A1A4iFMmkSy5RGjgyhuK5KHANILWiU3IWccXHjZ/i3Ea9nHGTrW2 aJRj1VKW/SyMgtQKWhizSw501emnVL260KvrxDp8UxYK0Rsit0f1wWf0VfNgAxdC+Syz hSzEUvGG26tzVs4UPtzzxsGlh6ulo4bVy6FTPd1iseiIRxmpe+Nd1SOPV4UAsL9wDoh6 D6cg8s55rhaquTeZa5h8tNvBqNOA7aLCaNFVgoe29anq7DNwHViQ0rQH6gfSJGwd2oFv cdVNpo0hcTUTx+ZJoWrqZ/2HiDOw6mxLfTLXO0Vq2hM+UglZZbUNifJy4RkwKrCeh9XK 2Q6g== MIME-Version: 1.0 Received: by 10.52.173.83 with SMTP id bi19mr3198137vdc.15.1333409374299; Mon, 02 Apr 2012 16:29:34 -0700 (PDT) Received: by 10.220.189.201 with HTTP; Mon, 2 Apr 2012 16:29:34 -0700 (PDT) In-Reply-To: References: Date: Mon, 2 Apr 2012 18:29:34 -0500 Message-ID: Subject: Re: 9.1.3: launching streaming replication From: Michael Nolan To: "Welty, Richard" Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary=bcaec51b9be51864d504bcba90e8 X-Pg-Spam-Score: -2.7 (--) X-Archive-Number: 201204/39 X-Sequence-Number: 186352 --bcaec51b9be51864d504bcba90e8 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Apr 2, 2012 at 6:19 PM, Michael Nolan wrote: > > > > I got similar messages the first few times I tried to start up my slave > server, I never did figure out exactly what caused it. > > One possibility is that I may not have restarted the master server after changing the postgresql.conf file, thus the server still didn't know it was going into hot-standby mode. -- Mike Nolan --bcaec51b9be51864d504bcba90e8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, Apr 2, 2012 at 6:19 PM, Michael = Nolan <htfoot@gmai= l.com> wrote:



I got similar messages the first few= times I tried to start up my slave server, I never did figure out exactly = what caused it.


One possibility is that I may not have rest= arted the master server after changing the postgresql.conf file, thus the s= erver still didn't know it was going into hot-standby mode.
--
Mike Nolan
--bcaec51b9be51864d504bcba90e8-- From rwelty@ltionline.com Tue Apr 3 15:44:02 2012 Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 88C78DE314D for ; Tue, 3 Apr 2012 12:44:02 -0300 (ADT) Received: from 66-109-41-228.tvc-ip.com ([66.109.41.228] helo=mx1-sch.ltionline.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SF5tj-0002LU-HT for pgsql-general@postgresql.org; Tue, 03 Apr 2012 15:44:01 +0000 X-ASG-Debug-ID: 1333467820-7fa101c20000-zW6XKP X-Barracuda-URL: http://10.1.1.20:8000/cgi-bin/mark.cgi Received: from ltischx01.lti.int (localhost [127.0.0.1]) by mx1-sch.ltionline.com (Spam Firewall) with ESMTP id E40E33988B7; Tue, 3 Apr 2012 11:43:40 -0400 (EDT) Received: from ltischx01.lti.int ([192.168.161.15]) by mx1-sch.ltionline.com with ESMTP id COsCHH7Z0YctBEm1; Tue, 03 Apr 2012 11:43:40 -0400 (EDT) X-Barracuda-Envelope-From: rwelty@ltionline.com X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD11B0.9D0B4CE1" X-ASG-Orig-Subj: RE: [GENERAL] 9.1.3: launching streaming replication Subject: Re: 9.1.3: launching streaming replication Date: Tue, 3 Apr 2012 11:42:24 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [GENERAL] 9.1.3: launching streaming replication Thread-Index: Ac0RJyc98S+7LlhET0+JvyW/2YDmLgAiTYQb References: From: "Welty, Richard" To: "Michael Nolan" Cc: X-Barracuda-Connect: UNKNOWN[192.168.161.15] X-Barracuda-Start-Time: 1333467820 X-Barracuda-Virus-Scanned: by Barracuda Spam & Virus Firewall at ltionline.com X-Pg-Spam-Score: -0.9 (/) X-Archive-Number: 201204/58 X-Sequence-Number: 186371 This is a multi-part message in MIME format. ------_=_NextPart_001_01CD11B0.9D0B4CE1 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable thanks for the suggestions. the light has gone on and i have it working = as of about 15 minutes ago. i'm going to revisit the documentation and = possibly make suggestions about making things a little clearer, or else = issue a mea culpa about my reading comprehension. don't know which just = yet. richard -----Original Message----- From: Michael Nolan [mailto:htfoot@gmail.com] Sent: Mon 4/2/2012 7:19 PM To: Welty, Richard Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] 9.1.3: launching streaming replication =20 On Mon, Apr 2, 2012 at 4:21 PM, Welty, Richard = wrote: I got similar messages the first few times I tried to start up my slave server, I never did figure out exactly what caused it. You can either delete all the files on the slave and try again, or do = what I did, write a script that handles transferring just the files needed to resync the slave. Here's the script I've been using to transfer the files between my two servers to resync them. This is not a production-ready script. I have a second tablespace, so there are two 'data' transfers plus the = xlog transfer. (You may run into issues transferring the pg_tblspc = directory, as I did, hence the '-safe-links' parameter.) The '-delete' term deletes any files on the slave that aren't on the server, unless you list them = in an '--exclude' clause.) /usr/local/pgsql/bin/psql -c "select pg_start_backup('tardir',true)" postgres postgres rsync -av --exclude log.out --exclude postgresql.conf \ --exclude postgresql.pid --delete --exclude pg_hba.conf \ --exclude pg_xlog --exclude server.crt --exclude server.key \ --exclude restore.conf --exclude restore.done \ --safe-links /usr/local/pgsql/data/ postgres@xxx:/usr/local/pgsql/data rsync -av /usr/local/pgsql/data2/ postgres@xxx:/usr/local/pgsql/data2 /usr/local/pgsql/bin/psql -c "select pg_stop_backup()" postgres postgres rsync -av /usr/local/pgsql/data/pg_xlog = postgres@xxx:/usr/local/pgsql/data/ echo "ok to start standby" -- Mike Nolan ------_=_NextPart_001_01CD11B0.9D0B4CE1 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [GENERAL] 9.1.3: launching streaming replication

thanks for the suggestions. the light has gone on and = i have it working as of about 15 minutes ago. i'm going to revisit the = documentation and possibly make suggestions about making things a little = clearer, or else issue a mea culpa about my reading comprehension. don't = know which just yet.

richard

-----Original Message-----
From: Michael Nolan [mailto:htfoot@gmail.com]
Sent: Mon 4/2/2012 7:19 PM
To: Welty, Richard
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] 9.1.3: launching streaming replication

On Mon, Apr 2, 2012 at 4:21 PM, Welty, Richard = <rwelty@ltionline.com> wrote:

I got similar messages the first few times I tried to start up my = slave
server, I never did figure out exactly what caused it.

You can either delete all the files on the slave and try again, or do = what
I did, write a script that handles transferring just the files needed = to
resync the slave.

Here's the script I've been using to transfer the files between my = two
servers to resync them. This is not a production-ready script.

I have a second tablespace, so there are two 'data' transfers plus the = xlog
transfer.  (You may run into issues transferring the pg_tblspc = directory,
as I did, hence the '-safe-links' parameter.) The '-delete' term = deletes
any files on the slave that aren't on the server, unless you list them = in
an '--exclude' clause.)

/usr/local/pgsql/bin/psql -c "select = pg_start_backup('tardir',true)"
postgres postgres

rsync -av --exclude log.out --exclude postgresql.conf \
--exclude postgresql.pid --delete --exclude pg_hba.conf \
--exclude pg_xlog --exclude server.crt --exclude server.key \
--exclude restore.conf --exclude restore.done \
--safe-links /usr/local/pgsql/data/ = postgres@xxx:/usr/local/pgsql/data

rsync -av /usr/local/pgsql/data2/ = postgres@xxx:/usr/local/pgsql/data2

/usr/local/pgsql/bin/psql -c "select pg_stop_backup()" = postgres postgres

rsync -av /usr/local/pgsql/data/pg_xlog = postgres@xxx:/usr/local/pgsql/data/

echo "ok to start standby"

--
Mike Nolan

------_=_NextPart_001_01CD11B0.9D0B4CE1-- From htfoot@gmail.com Tue Apr 3 22:21:59 2012 Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 30237DE314E for ; Tue, 3 Apr 2012 19:21:59 -0300 (ADT) Received: from mail-vb0-f46.google.com ([209.85.212.46]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SFC6w-0006v3-5q for pgsql-docs@postgresql.org; Tue, 03 Apr 2012 22:21:58 +0000 Received: by vbbff1 with SMTP id ff1so151967vbb.19 for ; Tue, 03 Apr 2012 15:21:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=coM6Wh+7tC/b8DR7B2LoTAMOEyeGwU/DpSz22BA+olk=; b=cg2HzOMQAccgBwRdtoLJRtzPkvD4iSHUsSqmY5IPTNgPZ/vC8SyifzXwouh4QR4dAA GAjanz/u7FyxUb6i+Up4/qioA/OBWTsnHDJ20EYescd4hAYhTkgQNQlG+reD59eZeYBW 0pOO2yXBKt8FFdT3raDKUTOSHbRuldYGfGhePLdTEniqkTDkoj2HXimIekLndyRkkWI/ zpLFvMRoxhgyxMgli0UVqyoEWEDhfB0gypzLBZ+BtB+0wptY8T+dkCLt5O/g2s3JaX9q OJUlUS9rWcbJEpDFmpEwHn0Fqq5tJLJ1G7+2Z8aa+YmjtmAjtHXgWp1PtMs82hZbx9zj evMA== MIME-Version: 1.0 Received: by 10.52.240.171 with SMTP id wb11mr5614653vdc.106.1333491705591; Tue, 03 Apr 2012 15:21:45 -0700 (PDT) Received: by 10.220.189.201 with HTTP; Tue, 3 Apr 2012 15:21:45 -0700 (PDT) In-Reply-To: References: Date: Tue, 3 Apr 2012 18:21:45 -0400 Message-ID: Subject: Fwd: [GENERAL] 9.1.3: launching streaming replication From: Michael Nolan Cc: pgsql-docs@postgresql.org Content-Type: multipart/alternative; boundary=20cf307ca3dc6c372e04bccdbb89 X-Pg-Spam-Score: -1.6 (-) X-Archive-Number: 201204/2 X-Sequence-Number: 7256 --20cf307ca3dc6c372e04bccdbb89 Content-Type: text/plain; charset=ISO-8859-1 ---------- Forwarded message ---------- From: Welty, Richard Date: Tue, Apr 3, 2012 at 5:33 PM Subject: RE: [GENERAL] 9.1.3: launching streaming replication To: Michael Nolan ** >you may want to do something with the other, then, as it's what came up when i went searching >for help. to amplify, the other page comes up first in a google search for "postgresql streaming replication" which is how i found it. richard Not sure how I found the other page first, but I'll look at that page, it looks like it hasn't been updated for 9.1 yet, either. It also doesn't show up in the topic category page for replication. http://wiki.postgresql.org/wiki/Category:Replication I don't how to update that one (or if that's left up to the administrators), so I'm sending this note on to the pgsql-docs list as well. -- Mike Nolan --20cf307ca3dc6c372e04bccdbb89 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

---------- Forwarded message ----------<= br>From: Welty, Richard <rwelty@ltionline.com>
Date: Tue, Apr 3, 2012 at 5:33 PM
Subject: RE: [GENERAL] 9.1.3: launchin= g streaming replication
To: Michael Nolan <htfoot@gmail.com>


>you may want to do somethin= g with the other, then, as it's what came up when i went searching >= for help.

to amplify, the other page comes up first in a google search for "post= gresql streaming replication" which is how i found it.

richard

Not sure how I found the other page first, but I'll look at that = page, it looks like it hasn't been updated for 9.1 yet, either.=A0 It a= lso doesn't show up in the topic category page for replication. http://wiki.postg= resql.org/wiki/Category:Replication

I don't how to update that one (or if that's left up to the adm= inistrators), so I'm sending this note on to the pgsql-docs list as wel= l.
--
Mike Nolan
--20cf307ca3dc6c372e04bccdbb89-- From greg@2ndQuadrant.com Tue Apr 3 23:30:44 2012 Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 6AA85DE314F for ; Tue, 3 Apr 2012 20:30:44 -0300 (ADT) Received: from moutng.kundenserver.de ([212.227.126.171]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SFDBR-0003Dj-UD for pgsql-docs@postgresql.org; Tue, 03 Apr 2012 23:30:43 +0000 Received: from [192.168.1.6] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MVYtf-1Ribm71wVT-00YvrJ; Wed, 04 Apr 2012 01:30:28 +0200 Message-ID: <4F7B8813.5020908@2ndQuadrant.com> Date: Tue, 03 Apr 2012 19:30:27 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111120 Icedove/3.1.16 MIME-Version: 1.0 To: pgsql-docs@postgresql.org, htfoot@gmail.com Subject: Re: Fwd: [GENERAL] 9.1.3: launching streaming replication References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:IGlkoZuiZdHmaP3XFllEQD8e2jlsG+n3G37qWmy7SwM C6NWIW3qY/x1NHlwxoqGuQ5alwec8H3SVhqPLlwGQp1pZ88Sb7 rvafV8uftEWa/X9oq4uf8NNUMpkzWpDCHmuR0xDXS2QVPK/JZN PqvtQDrlbWeSKJQT+f02g7UJUbVOksjRpV3loZw2jClAtujWMj LKOSWlQ1D2WRF7nYwlpljG1ZfZD4c1vdWVO7zl9q0Xi3VxnX81 ltfCjr9JtbOiwgSEPk9dTQ8tqLWvlrB9dZFkoAcFaNFqlUMYmp hB+wYgGDHnVnGwIyxlVopf6b8UjgqlQqusZrhSMCL0NjALjodT F1yVHarDrbuO+yAJHGCc= X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201204/3 X-Sequence-Number: 7257 On 04/03/2012 06:21 PM, Michael Nolan wrote: > > From: *Welty, Richard* > > to amplify, the other page comes up first in a google search for > "postgresql streaming replication" which is how i found it. > > Not sure how I found the other page first, but I'll look at that page, > it looks like it hasn't been updated for 9.1 yet, either. It also > doesn't show up in the topic category page for replication. > http://wiki.postgresql.org/wiki/Category:Replication Mike already fixed the category problem himself. I just updated http://wiki.postgresql.org/wiki/Streaming_Replication so that it suggests users visit the official docs and tutorial on the wiki, since we can't just make Google unlike that page easily. P.S. Mike: please fill in the "Summary" box about what you're changing when you update wiki content, or click the "This is minor edit" box if there's no serious content change. Streams of edits with no description are hard to tell from spam. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com From htfoot@gmail.com Wed Apr 4 15:18:46 2012 Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 244BC4BB8EB for ; Wed, 4 Apr 2012 12:18:46 -0300 (ADT) Received: from mail-vb0-f46.google.com ([209.85.212.46]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SFRyp-0002ie-Pf for pgsql-docs@postgresql.org; Wed, 04 Apr 2012 15:18:45 +0000 Received: by vbbff1 with SMTP id ff1so226090vbb.19 for ; Wed, 04 Apr 2012 08:18:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9wauwt4itnCqccjDAbLfFtgLL6IxT9yRk+ng86VZVQE=; b=nx3uPJW6oVpTRuGgT4PSi2LF+jh0sofB71LN9A8JunXrkkhuoiQEiBFAtB/UaXx39W KnWHeW2UZMCUfvbuIfuAJbuH5lYejAWcEb5pCPoBerYzlBeylEr41vaWOXczzkwsvPrb jTZSUPl8uUqOVWdDEO01T0Lr4RnUO+KWxuxXAeJfK9ZTF659GPpOD33UHp16rvTs7X5/ TEF2IYAfCTmlOp+Lmm5cRY94w5PjV0rIyhPnBZQSkuLG1Kdn8KD/Qr8BAULXlKpr6KD/ Nd5ovg9lblgV6oqoaXMmGGgb73+KVNzbecSKAbK9tVZkKOKJKOnOC8N3So6W7GmIRkjC q3Hw== MIME-Version: 1.0 Received: by 10.52.173.83 with SMTP id bi19mr5876188vdc.15.1333552706663; Wed, 04 Apr 2012 08:18:26 -0700 (PDT) Received: by 10.220.189.201 with HTTP; Wed, 4 Apr 2012 08:18:26 -0700 (PDT) In-Reply-To: <4F7B8813.5020908@2ndQuadrant.com> References: <4F7B8813.5020908@2ndQuadrant.com> Date: Wed, 4 Apr 2012 11:18:26 -0400 Message-ID: Subject: Re: Fwd: [GENERAL] 9.1.3: launching streaming replication From: Michael Nolan To: Greg Smith Cc: pgsql-docs@postgresql.org Content-Type: multipart/alternative; boundary=bcaec51b9be55eb63604bcdbeff2 X-Pg-Spam-Score: -2.7 (--) X-Archive-Number: 201204/4 X-Sequence-Number: 7258 --bcaec51b9be55eb63604bcdbeff2 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Apr 3, 2012 at 7:30 PM, Greg Smith wrote: > Mike already fixed the category problem himself. I just updated > http://wiki.postgresql.org/wiki/Streaming_Replication so that it suggests > users visit the official docs and tutorial on the wiki, since we can't just > make Google unlike that page easily. > Greg, there's sort of an inconsistency between the developer-oriented streaming replication page and the tutorial. The streaming replication page says to copy the entire data directory, which would include the WAL logs in the pg_xlog directory. The 5 minute version in the binary replication tutorial skips that directory, the longer one copies it separately, after the backup is complete, so that the slave can perform any committed changes as part of syncing up with the master. I assume that there is no harm in copying the pg_xlog directory in the 5 minute version, and it was left out as a time-saver. However, if the master fails and the slave has to take over, wouldn't it need the pg_xlog directory? If it hasn't been created, could that cause problems or would the backend know to create it? -- Mike Nolan --bcaec51b9be55eb63604bcdbeff2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Apr 3, 2012 at 7:30 PM, Greg Smi= th <greg@2ndqu= adrant.com> wrote:
=A0
Mike already fixed the category problem himself. =A0I just updated http://wiki.postgresql.org/wiki/Streaming_Replication so that it sugg= ests users visit the official docs and tutorial on the wiki, since we can&#= 39;t just make Google unlike that page easily.

Greg, there's sort of an inconsistency between t= he developer-oriented streaming replication page and the tutorial.

T= he streaming replication page says to copy the entire data directory, which= would include the WAL logs in the pg_xlog directory.=A0 The 5 minute versi= on in the binary replication tutorial skips that directory, the longer one = copies it separately, after the backup is complete, so that the slave can p= erform any committed changes as part of syncing up with the master.=A0

I assume that there is no harm in copying the pg_xlog directory in the = 5 minute version, and it was left out as a time-saver.=A0 However, if the m= aster fails and the slave has to take over, wouldn't it need the pg_xlo= g directory?=A0 If it hasn't been created, could that cause problems or= would the backend know to create it?=A0
--
Mike Nolan=A0
--bcaec51b9be55eb63604bcdbeff2--