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 1tcdXU-001YaH-AX for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Jan 2025 04:49: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 1tcdXT-00GUAy-De for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Jan 2025 04:49:27 +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 1tcdXT-00GUAq-1D for pgsql-hackers@lists.postgresql.org; Tue, 28 Jan 2025 04:49:27 +0000 Received: from mail-ej1-x636.google.com ([2a00:1450:4864:20::636]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tcdXQ-001sXT-1e for pgsql-hackers@lists.postgresql.org; Tue, 28 Jan 2025 04:49:25 +0000 Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-aaec111762bso1137728066b.2 for ; Mon, 27 Jan 2025 20:49:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738039763; x=1738644563; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=2QXQj76r8CezjIuLmiu+rEIK82TuR9STEf+JXTJnDrg=; b=Mu0Zo8+lFUAzcTzVDmHjZ9uHkpBMsGoFaD1CEeF/XI3ppW7Hg53AclHMY5Kx8PME7C yuW14Kt6Sa6HGn2JXmfdKRbfeh/EMyN6BosRkO9kpdNwcClRaydYA7RizxEajGmviK7j /Yr/ZqcXUYHL7WeOFTv6RITM1bUQtpSPFUiPON6pEzbwsNCitYg6OMS+q16UP+qLX7uO VSPj7AJAhluaa0LsLPjBwxR3qG//IxkUnSIkKbq8NBTs9LxKzzBBQstshVg+yhCbGLIM meJceeZS0rqJy8KslMoBZSTGrVAZE6Z2zjuRnqHFo7R1FztTLFZn0/zl18HkobwAN1e9 JCrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738039763; x=1738644563; h=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=2QXQj76r8CezjIuLmiu+rEIK82TuR9STEf+JXTJnDrg=; b=Mk470hHrbKg9v6u0xjf43IXztudZG+yxRa11PiqSYpLg5xn7b8H6gccyfcZ0k7PbwU 9xz9a7AZmetG9IliGasC7sSu3sR7xgCnD0pOPtntd+a2zvKJotBnefcr5jl/h3xkBufq lZp/cAs8gAba+zAJkqPmXZ6S+D/VAsEs+93KWBU/vUxWoeQmviNMfRv1uXoedHAPSC9I yOWGupqqFLeGpO4zHTaTsrnDVi4HyIZyWjUK2qAUI6zFzqZOnNCtf3qqLGDDNts7C4Q7 ulq3y8y4MlucSe6cKkKh+n9w8BOaiBZXaiUsCSOCvJu3S4z6ko7hmv3+fxV8z1n6KRB7 ff0A== X-Forwarded-Encrypted: i=1; AJvYcCWrflgsINh0lBumGp9H6OJfyFUCScy7El/8WI052a8rG3++6rOuJQNxJ1ViYVFSm5dNnqTYIZWbwE+na1pd@lists.postgresql.org X-Gm-Message-State: AOJu0YyC6eJPWcOZwfPR5rKE0HPxm36XxfCtKlY1Gr1NKh+HM5zqq8DR RbPFU8UiNJOTcJDgHhexRUHjMTBau8HpIfxD1lDwL2vPQJ6igYYwE0mt3Xg9DN+epEcngGws4HU 90k1Bi/PCMes0GoSwQO6zMxGzg0I= X-Gm-Gg: ASbGncueU4/1VIgi8dZtJXi4MqAI2h1VEuuMrGIj+W6Iz1l/T49f3QVlEZw7Wnc/z1X 6qLQjoWj4yOzhzJX5Pb72HdX143uNjr25crVXsHABQxQX4fpB2LNndhtT5x5QaJYXwGP/T7sE7J w= X-Google-Smtp-Source: AGHT+IGl7WG1XI3YpJj6ZFEEOksExb7Qj3DA8Mf6eMSnRHFMALemLxLBzAhPNzwhh3Y+oy0FdYtNplrL651DEcZeLjc= X-Received: by 2002:a17:907:70a:b0:aa6:93c4:c68f with SMTP id a640c23a62f3a-ab38b10cf92mr3619750966b.21.1738039763163; Mon, 27 Jan 2025 20:49:23 -0800 (PST) MIME-Version: 1.0 References: <202501110844.5ztsym4vbflm@alvherre.pgsql> In-Reply-To: From: Srinath Reddy Date: Tue, 28 Jan 2025 10:19:11 +0530 X-Gm-Features: AWEUYZlJQs9z9nIQL_LIaDmNwE5x3eS57r0ovrUlpjmTYORmF2GY-ReI3WbJ5jk Message-ID: Subject: Re: Non-text mode for pg_dumpall To: Mahendra Singh Thalor , pgsql-hackers@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000b060fb062cbcea21" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b060fb062cbcea21 Content-Type: text/plain; charset="UTF-8" Hi mahendra, I have reviewed the code in the v11 patch and it looks good to me. But in common_dumpall_restore.c there's parseDumpFormat which is common between pg_dumpall and pg_restore ,as per the discussion in [1] thread i don't think we should create a common api ,as discussed in the thread there might chances in the future we might decide that some format is obsolete and desupport it in pg_dumpall ,while support in pg_restore for compatibility reasons. [1] https://www.postgresql.org/message-id/flat/CAFC%2Bb6pfK-BGcWW1kQmtxVrCh-JGjB2X02rLPQs_ZFaDGjZDsQ%40mail.gmail.com Regards, Srinath Reddy Sadipiralla, EDB: http://www.enterprisedb.com --000000000000b060fb062cbcea21 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi mahendra,

I have reviewed the code in the v1= 1 patch and it looks good to me.

But in common_dumpall_restore.c the= re's=C2=A0 parseDumpFormat which is common between pg_dumpall and pg_re= store ,as per the discussion in [1] thread i don't=C2=A0think we should= =C2=A0create a common api ,as discussed in the thread there might chances i= n the future we might=C2=A0decide that some format is obsolete and desuppor= t it in pg_dumpall ,while support in pg_restore for compatibility=C2=A0reas= ons.

[1]=C2=A0htt= ps://www.postgresql.org/message-id/flat/CAFC%2Bb6pfK-BGcWW1kQmtxVrCh-JGjB2X= 02rLPQs_ZFaDGjZDsQ%40mail.gmail.com

Regards,
Srinath Reddy Sa= dipiralla,
EDB:=C2=A0http://www.enterprisedb.com
--000000000000b060fb062cbcea21--