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 1tkFFc-001nk1-Cx for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Feb 2025 04:30:28 +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 1tkFFa-006SGx-R3 for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Feb 2025 04:30:26 +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 1tkFFa-006SGo-HG for pgsql-hackers@lists.postgresql.org; Tue, 18 Feb 2025 04:30:26 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tkFFY-001RnF-2a for pgsql-hackers@lists.postgresql.org; Tue, 18 Feb 2025 04:30:25 +0000 Received: by mail-ej1-x62d.google.com with SMTP id a640c23a62f3a-abb94e3b49bso307333066b.3 for ; Mon, 17 Feb 2025 20:30:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739853023; x=1740457823; 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=lj3n+wG2Xtj/XH89Ia3qwy3F2aSOIVESTrlIWdmwGZ4=; b=IfKkLKFvvz/T+8a2xj9lNSMZSk5dG9a3Lu91Gy+zzLvAq5yXxc42RN6aNHdoF1PDAT pWed5tgF5Y2j+MY9LnvzrHqwHdf1KIGgmNguXdKTlTUaQ3aoU/0ETbwhMJPppiXZRTnD gMgUat2QF8hR8gsRkT2wt/m8uQWpvZvNw0AE3Cw5/wfyClZRqFW4esXjzpIhImBAH6wy 1w4rT6+k4mlmyRGEco0djnpkk6xLWSPXudNG1AItibMRQ74lXFxj/CE4iLBfSbKMBmXa LR6SRyUBcrBBNGmk3yT4Y9TR9XaXeXSNlC+hG3mq7aVJRpQ7rsOlFcWpHuuAipAdgNtD IPrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739853023; x=1740457823; 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=lj3n+wG2Xtj/XH89Ia3qwy3F2aSOIVESTrlIWdmwGZ4=; b=lA3X4ATdJtsa+sS7UpYl3JPWQ5yhPkm0jg25edyMpwodAQu9oqfdleugqYd5L9UWaK NyYTb+Gk2jh3kqYyLrgyuYNtD0+AX+Rdi4gFbLvg4c57Ek/mQpSVdvwSqxKiDcJx7zo8 flPKCMnhMT7kdj9uAszgWsM+GHNoh21s1dIreUdQwVUD9F4Xz26K0axBSRSGI3fVVeeZ PBBpXRbPXVWX5m+q8CwzT4pNU7c/M121Ix9RSSZFYroAZ7UGgxxc0AvNPGSKQzKe3Unk ym/kxOSFDfTyZBCALplcANWGAMisIbyg5pPdKzxbZiXPlCYjzfPdbuC3zsrniFLNQram 7MPA== X-Gm-Message-State: AOJu0YxGkj4kQx3ECacALrNGrGpxLD70mFTCbYVqfEJ3PZXAFlUySXEf nCt4Z4hFd6+P392tdElHTLkdoLFod1Er1Iwwu+pby0nJLqEmcNQBY78By7zIa0o1UVdSBdkMHzj Qo8sYZrQMYG/dXugJyQ+sVt3O7AFdGSCbHAk= X-Gm-Gg: ASbGncskSSGNJJAk3qPE5S0z1GwKTZtgK4e7z9tbaZabh7Ql8hPveDrgbPHubZA9M5H JuBHR6j3dE1f7nURFwQU06GBcvSjtQTz3eiWKHfZcGq4NcEyvCkg7w7TmTWSRmlu4pk5jcVjaiv I= X-Google-Smtp-Source: AGHT+IE/z5bSln7E7fpntT10swl2h1f6njJWaAPX2YTJHKKuCq6WG1QfO5Z54njIFwAsrdawuITyHwKBFD3eOTc55E4= X-Received: by 2002:a17:907:7209:b0:ab6:d575:3c4c with SMTP id a640c23a62f3a-abb70d15d42mr1043034066b.17.1739853022828; Mon, 17 Feb 2025 20:30:22 -0800 (PST) MIME-Version: 1.0 References: <202501110844.5ztsym4vbflm@alvherre.pgsql> In-Reply-To: From: Srinath Reddy Date: Tue, 18 Feb 2025 10:00:11 +0530 X-Gm-Features: AWEUYZln2AKZZdZ1ovv7R60v8vS58tcXyXp6K9-Pxd8e0ivWSh_UvRm95cyScMM Message-ID: Subject: Re: Non-text mode for pg_dumpall To: Mahendra Singh Thalor , jian.universality@gmail.com Cc: pgsql-hackers@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000063241b062e63192b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000063241b062e63192b Content-Type: text/plain; charset="UTF-8" Hi, i think during restore we should not force user to use -C during cases like ./pg_restore pdd -g -f - ./pg_restore pdd -a -f - ./pg_restore pdd -s -f - because its not good to use -C to create database every time when we are using these options individually. latest patch throws following error for all the above cases pg_restore: error: -C/--create option should be specified when restoring multiple databases by archive of pg_dumpall pg_restore: hint: Try "pg_restore --help" for more information. pg_restore: hint: If db is already created and dump has single db dump, then use particular dump file. Thanks and Regards Srinath Reddy Sadipiralla EDB: https://www.enterprisedb.com Srinath Reddy Sadipiralla, --00000000000063241b062e63192b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
i think during restore=C2=A0we sho= uld not force=C2=A0user to use -C during cases like=C2=A0
./pg_restore p= dd -g -f -
./pg_restore pdd -a -f -
./pg_restore pdd -s -f -
becau= se its not good to use -C to create database every time when we are using t= hese options individually.
latest patch throws following error for all t= he above cases

Srinath Reddy Sadipiralla
EDB:=C2=A0https://www.enterpris= edb.com
Srinath Reddy Sadipiralla,<= /font>
--00000000000063241b062e63192b--