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 1u3FsY-00CwXQ-HJ for pgsql-general@arkaria.postgresql.org; Fri, 11 Apr 2025 15:01:14 +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 1u3FsW-00Avb1-TX for pgsql-general@arkaria.postgresql.org; Fri, 11 Apr 2025 15:01:13 +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 1u3FsV-00Avap-QJ for pgsql-general@lists.postgresql.org; Fri, 11 Apr 2025 15:01:12 +0000 Received: from fhigh-b2-smtp.messagingengine.com ([202.12.124.153]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u3FsR-004FuI-0j for pgsql-general@postgresql.org; Fri, 11 Apr 2025 15:01:11 +0000 Received: from phl-compute-12.internal (phl-compute-12.phl.internal [10.202.2.52]) by mailfhigh.stl.internal (Postfix) with ESMTP id 0B11B25401B4; Fri, 11 Apr 2025 11:01:06 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-12.internal (MEProxy); Fri, 11 Apr 2025 11:01:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1744383665; x=1744470065; bh=ULF3nbDrgO2EXMYLaRBWGkz1uQTnkCm/uOe59Kzmo6g=; b= PLpPL3IF6JBtCpmZK71mTzcvWoDfbs+jnpMNA3ax4g8ChWzUetSuYT8Slu7Inec/ 4eNM4iB6WqL0dLvUWh13eqlemWd/kUd+NeBMoquE22ucfSg4fPZNX36sg/5zSfNf yfMTisrY9qOus4hKjgaQuyVKIKDPa3FDSuE3i9+kT05zQ6OKKBjISIAwaeVV3ZgT L3xz8RkCwJepw9zxtPFMwwK7Pu5qUkvxaO6K6tXiM2lJ1Bh7Bjto6c0WZiJ79bXq wVQK72yS8KTyy8ls/nBWFLErDidYPXJYuayVg7hqGg6ZBCsQSf/YamvAP5E3h0uY BHyrQ50HlErLXDxdQvp9tA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1744383665; x=1744470065; bh=U LF3nbDrgO2EXMYLaRBWGkz1uQTnkCm/uOe59Kzmo6g=; b=ti9Ro+TfzoBASPUsC WkqEtnWNjkokZuQtepIdOmYoRa0yd4X34dUbi7GfkktO7ti33xGf8n7NXW5PN65p hkBxll+x/3tSQkHnPLI3qqaGUSyiJ0Dt1aajHR2LiWkChUfjSAB5Wy3txgYO3WLD vfZwNRhUHqYSjA+orN5Z8WXgzVud3lA4vsIgMYGKb6gWcxSfPHree2DrH676EGPw QP6Z92xo5cSzgDnjmC66fAW7fcq5CRG1q2Kmry39HCEzuk3h7eNjW3w9V3Faz3Ei AaGPQSoaKoZ/U/qOFjXtxjBgjmenX2y2Qo2r0yBmaPCiv1hPnLGPY4HrsWoOn3z3 pi/og== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvuddvudduucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggv pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpefkff ggfgfuvfhfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughrihgrnhcumfhlrghv vghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrf grthhtvghrnhepleegveekkeekueeigfdtveeileeuhfefudefteekjeffkeejueejheeg heegkedtnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghv vghrsegrkhhlrghvvghrrdgtohhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmth hpohhuthdprhgtphhtthhopehsihhvrghpohhsthhgrhgvsheshigrhhhoohdrtghomhdp rhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlsehpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 11 Apr 2025 11:01:05 -0400 (EDT) Message-ID: <40a86c92-5fc9-447d-969e-2a61cc98629c@aklaver.com> Date: Fri, 11 Apr 2025 08:01:04 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: To take backup of Postgresql Database without large objects To: "sivapostgres@yahoo.com" , Pgsql-general References: <1477036526.178965.1744376140698.ref@mail.yahoo.com> <1477036526.178965.1744376140698@mail.yahoo.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <1477036526.178965.1744376140698@mail.yahoo.com> 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 4/11/25 05:55, sivapostgres@yahoo.com wrote: > Hello, > > Using PostgreSQL 15.1, compiled by Visual C++ build 1914, 64-bit in > Windows 10. > > Trying to take backup of a database, using pg_dump, where one table > contains bytea datatype, which I don't want to include in the backup. > > My command was: > "E:\DBBackup\bin\pg_dump.exe"  -h 192.168.1.1 -p 5432 -U > --no-blobs -F c -v -f "E:\DBBackup\demo6_110420251637.bak" demo6 > > the backup includes the bytea field also. > > I tried with > "E:\DBBackup\bin\pg_dump.exe"  -h 192.168.1.1 -p 5432 -U -B > -F c -v -f "E:\DBBackup\demo6_110420251637.bak" demo6 > > also, which also included the bytea field. 1) Short version Short version bytea fields != large objects. 2) Long version From here: https://www.postgresql.org/docs/current/app-pgdump.html -B --no-large-objects --no-blobs (deprecated) Exclude large objects in the dump. When both -b and -B are given, the behavior is to output large objects, when data is being dumped, see the -b documentation. Where large objects are defined here: https://www.postgresql.org/docs/current/largeobjects.html > > What wrong I'm doing?  Couldn't figure it out.   Any help is appreciated. > > Happiness Always > BKR Sivaprakash > -- Adrian Klaver adrian.klaver@aklaver.com