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 1tsEi2-00Gu4a-4Q for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Mar 2025 05:32:50 +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 1tsEi0-00ESRo-T9 for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Mar 2025 05:32:48 +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 1tsEi0-00ESHZ-El for pgsql-hackers@lists.postgresql.org; Wed, 12 Mar 2025 05:32:48 +0000 Received: from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tsEhw-002MBf-0n for pgsql-hackers@lists.postgresql.org; Wed, 12 Mar 2025 05:32:45 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-6fd80f30ba5so44093037b3.3 for ; Tue, 11 Mar 2025 22:32:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741757563; x=1742362363; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=X5U5IWlo2dtQ/Conpcoc3A1I2ZuOYpkc79IeDIVWVUg=; b=AEDcWX6GxGGFVtn0QCHWtNQmwEewD7RxOim3bz4SyXHmkfwQSuRDqvaGTs7+MyL49R N2k4hs/bx3WR8fgAxBBhC7Dy6GvX113+XFZpcM6Pq7cInPC11jfnyTBfT9VOYFK8xlcd oZwZkA1iyG4Z8qWkxzFsOVK5iwA4e7xqAYUTSO+wqXJz5RYSihWi9+nIZtMivfnTsSWI CDXT7sAtDrwgWMlpiLcibN3ZofSiyhzFrc26+WZYb8RuwM00HLoVhFwmgCy/muQAIcpl 9TFC2R0dbZkrwGNUA8xQh08PTr+nx0i14WXxG3vgG4MSsLHPnj5XTfisOPwtN9lh+rkR 0HEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741757563; x=1742362363; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=X5U5IWlo2dtQ/Conpcoc3A1I2ZuOYpkc79IeDIVWVUg=; b=mTDPlgZ6XISG/wGYiozJQhvNTjo3HYKCtrZwICA+u4NoemHMJWkS3AfjGsCmeVnAQx K1qQ6SytydX3mgRDq/DD13LPu62l8kVI9tZFmvbtQNmnSvAkobeYSZqeRR2ifoEnUR+t PvencnpwVJ3XzDYujwigKX1XjE/FQuOA2N/xars7A3lOWsQZfz6P9ERkYWEejXg+saiu QrXnTBFcgQVdVVdT5x1LgueKksQVhfLv/LxiwJDGV1UEGYfAJUMvzT7pl3V43+DjKEU8 ObSIxTor5g495/B2/tBBYF+/P0LHtpeRCC41W9kJ59u5SmJiX0Qspoq70iLutT6GTgLQ T/pw== X-Forwarded-Encrypted: i=1; AJvYcCVY543MIFYSYzuhqkqGkyIYtTm1gxOZVZ7XrKd4hYkKDiFZcxccLf7F9JdJCTUh9SCNm0WVmaUa26CpcZ/8@lists.postgresql.org X-Gm-Message-State: AOJu0Ywce9GqxiCc5FTxRMX8NA8qBCa3n4wNXU7BAFSNmkKfW+G5ZLwd xsE8SfQ062z8GnHLFuh7UHfuZDHh9G1utb5cl3t8arQQsFvVOCkN3PIiZ7+mT73sVcKz3IPBzOv uQ8Rijyt7vMhe1GaIA6woNPGpF5Q= X-Gm-Gg: ASbGncs9YKc/MA6NCHq+PdxVILBkvmOcG4H5Tm1JpLaCVH0l0MV9JquaKr1bDUO1grw lKDawBJwtqfprSebPhEDWykmCkLv5GjuW4yeBh0WspjjifIVhhcwLMYYROGpHbYuTg05yOUVZkt /G9IKDcEYmzBJ+h6TIO5wwnzo1+VDtCmuB8Zt8uIk3oVxpp2W3BPtMGwRKyDZT X-Google-Smtp-Source: AGHT+IFo3G+fkpcyBCKU+75P48zGDxpe5CK0TZuyj48spMtX2t82n96DJKuBJPOA1yqmfCT3k5CQC3rLDidEedExzpE= X-Received: by 2002:a05:690c:48c2:b0:6fe:b88e:4d86 with SMTP id 00721157ae682-6febf2b4385mr243784447b3.9.1741757563640; Tue, 11 Mar 2025 22:32:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: vignesh C Date: Wed, 12 Mar 2025 11:02:32 +0530 X-Gm-Features: AQ5f1JqUTCfSByw-Ysnq_RaUtjvot2Ro3TtYFAc1bjEWI0VHsUdwWvY8URI5WXQ Message-ID: Subject: Re: pg_recvlogical requires -d but not described on the documentation To: "Hayato Kuroda (Fujitsu)" Cc: Ashutosh Bapat , "pgsql-hackers@lists.postgresql.org" Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 21 Feb 2025 at 14:25, Hayato Kuroda (Fujitsu) wrote: > > Dear Ashutosh, > > Thanks for the reply. > > > > ISTM the inconsistency is introduced since the initial commit. I think they should > > be unified either > > > 1) update the doc or 2) accept when -d is not specified. Personally, I like 2nd > > approach, pg_recvlogical > > > can follow the normal connection rule. I.e., > > > > > > > Given that the discrepancy has survived so long, it seems that users > > always pass -d. And to some extent, requiring users to specify a > > database instead of defaulting to one is safer practice. This avoids > > users fetching changes from unexpected database/slot and cause further > > database inconsistencies on the receiver side. I would just fix > > documentation in this case. > > Something like attached, right? Apart from the database, I believe the target file also needs to be specified. Should we include this option also along with dbname: + + + + + + dbname + pg_recvlogical -U postgres --start -S test -d postgres pg_recvlogical: error: no target file specified Regards, Vignesh