Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvTDx-005ONq-Tk for pgsql-general@arkaria.postgresql.org; Wed, 25 Oct 2023 02:02:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qvTDw-00FKhM-8x for pgsql-general@arkaria.postgresql.org; Wed, 25 Oct 2023 02:02:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvTDv-00FKhE-Uq for pgsql-general@lists.postgresql.org; Wed, 25 Oct 2023 02:02:19 +0000 Received: from mail-yb1-xb31.google.com ([2607:f8b0:4864:20::b31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qvTDq-002AIA-Hv for pgsql-general@lists.postgresql.org; Wed, 25 Oct 2023 02:02:18 +0000 Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-d9caf5cc948so4744762276.0 for ; Tue, 24 Oct 2023 19:02:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698199333; x=1698804133; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=S0G2pNsfnlB92CfafjQSdY19sSYbzAGCYfORGzE8UTg=; b=VQzVHF+Dxjq02mQwEV0wjaS62ShpFm6x73Vei+0l2e1snsDvC+BiUTetZp2WPTtli9 G5J1MqbljD/gJ1TFW4KgeP9jMie4qfI0+HGwndqIzrDQ+SZ6apDFl8lE5lu3nSGaYb0O cvfDVgXD0CyJK/91SONkSoHpDOAEFH73myktU0Rm6cQbkbss/CBBjIFgb1Xs2JbxPT0/ YpamIfQGW70O8h1I4/Wr2ZVK9h6iQBn3bDRlIY53l0qMft0gN306VqOoQzZYe2sgxuVE Mi7rke67qpEs/N03JlvV6VfrqDjmrNA+CwT1yBrmNuFV/SAX9QzgxItK3PD9kAHLhfRL PhaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698199333; x=1698804133; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=S0G2pNsfnlB92CfafjQSdY19sSYbzAGCYfORGzE8UTg=; b=B8YrJfY7ZdMR6jk4C4j0EE4bAEz51ZAO3AZ+fxuyVl+rXinrZGvDdpU9a94vUhuRe+ sr+ujSt7Vybs2XFHZdisLRkT2yKUd9WH+wNbZT7kDnqeD8yc4IBG2u/lO+hje2tRDpB2 Kq+EiOEKyWR6kCWf18ICNnoLfZCGU7Ac73f/EfXb1pSYiK6Q42XLW6gv3VdCYVEUf4FE ngQg+kGR153ddKvYALBwl9/FH24O/Lrk+SM2kzlYtsp50HglGFzozvxzWtwHQDr5YVg5 YtOeR8e78080k9Xls3FQjwJsbmHJWSNXk6oPll0SZB01Q/g034iUg8VsmWhYNny3dZtZ UGVA== X-Gm-Message-State: AOJu0Ywt1M3cTGRd8Rp5No5DxeOzidS37Q42YS4y8e7VOEUrybFasG9G m1Cp0p0PQPTPC+u6ZmsfK+/g8ab/mSo= X-Google-Smtp-Source: AGHT+IG2JtzgchWUtn3BSP883qdII9q2z1+H1WvruKZ3yLki3sWcyjPOIVIKnf8K9DunPJDsQWBxgg== X-Received: by 2002:a25:b287:0:b0:d9c:df27:7012 with SMTP id k7-20020a25b287000000b00d9cdf277012mr13139441ybj.43.1698199333464; Tue, 24 Oct 2023 19:02:13 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:990b:551:8028:180e? ([2600:1700:bd2c:b810:990b:551:8028:180e]) by smtp.googlemail.com with ESMTPSA id p85-20020a254258000000b00d7e339ada01sm4043966yba.20.2023.10.24.19.02.12 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 24 Oct 2023 19:02:12 -0700 (PDT) Message-ID: Date: Tue, 24 Oct 2023 21:02:12 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: setting up streaming replication, part 2 Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Ron In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/24/23 19:29, Brad White wrote: > I have the replication server set up and the streaming is working. > The latest data show up, as desired. > > 3 minor issues. > > 1) I also have the WAL files being copied to a common location from the > primary server with >       archive_command = 'copy %p > "\\\\DISKSTATION\\AccessData\\Prod\\WALfiles\\%f"' > > It's not clear to me how the replication server finds those files. It doesn't, because streaming replication continuous streams WAL records. > > I also have the cleanup set to go, but it doesn't seem to be cleaning up > any of the archived files. >     archive_cleanup_command = 'pg_archivecleanup > \\\\DISKSTATION\\AccessData\\Prod\\WALfiles %r' > > 2) I have the connection string set for the replication server to connect, >      primary_conninfo = 'host = 192.168.1.112 port = 5433 user = > {pg_rep_user }password = {password}' > But the log file shows >     LOG:  waiting for WAL to become available at 2/A10000B8 >     FATAL:  could not connect to the primary server: connection to server > at "{IP}", port 5433 failed: fe_sendauth: no password supplied But you said that streaming is working. > 3) When I run >     "C:\Program Files\PostgreSQL\15\bin\pg_ctl.exe" promote -D "C:\Program > Files\PostgreSQL\15\data" > on the backup to promote it to Primary, I get >     pg_ctl: could not send promote signal (PID: 3996): Operation not permitted > > Thanks for all the help so far, > Brad. -- Born in Arizona, moved to Babylonia.