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 1sEYvu-002ACu-Hm for pgsql-admin@arkaria.postgresql.org; Tue, 04 Jun 2024 18:30:55 +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 1sEYvt-001pMj-8p for pgsql-admin@arkaria.postgresql.org; Tue, 04 Jun 2024 18:30:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sEYvs-001pMb-U5 for pgsql-admin@lists.postgresql.org; Tue, 04 Jun 2024 18:30:52 +0000 Received: from mail-pf1-x42d.google.com ([2607:f8b0:4864:20::42d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sEYvm-002L55-1e for pgsql-admin@lists.postgresql.org; Tue, 04 Jun 2024 18:30:52 +0000 Received: by mail-pf1-x42d.google.com with SMTP id d2e1a72fcca58-702555eb23bso2820182b3a.1 for ; Tue, 04 Jun 2024 11:30:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717525844; x=1718130644; darn=lists.postgresql.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=D+cL3fQgk+vMdDt/jtnWJeG4lDPd7e1aAakKpV9DL0w=; b=FaCTjj/oN4LTtO7pC6XFnMmW55TIVx/skl02KEz364QBz2GqiTT8mxF3hA2kvKMei7 JFp11VOyW33RQnreaaIyrMmvyS0hBOByAURWcxigIuRQ1CLx6Ten6GzqTjQG4IZdsxaJ 1jFDdag6BEeReHjFfaluY+fmQLiPQ3RFyXUI8h9KQLt0cPTpJK7iqQmLwdLEdj+p+Zjw Qc0zT0+s+svEs8Gh0se7iA0GyXcs0T+kUlAHv3VpvfKRbn0o1rEZTjHuHoBhyIvuLnMC XNAQQycKJ6LcoK/euB8OVT46o3CeAOAAiIgA4eJZjetrOo0UXTu9K9yZbCy5pPieOvQc Vmng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717525844; x=1718130644; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=D+cL3fQgk+vMdDt/jtnWJeG4lDPd7e1aAakKpV9DL0w=; b=Lr9RPfqVS7iefqUvBhSJNQdLJuvRyKHJrNiQQkfpSG0pIQ92166XaqT/Z/1GNbOms3 UWYGNJiNiREa7oZCMrMkg+rUm7sT4o/x/q47Tdv4uzAb577wOGPotLVr4Y7G6ZApt/Ky /2hnjiqgh2PMsNbutKrzDkb+vXZpIuuLJ7PrdePDAfSJo259H49xHLGycUWMjFZ6HTjU WsqWdaX9/gLZb3RTaL/8hPQIIKqkyaPHV2UeEYasga4yh7r29+24sH33pJNEPdO3Jbze L4k7eFDA5kzeaO9IoWvbUlwYUNTqw8v37lOrPxMcntntyYh1ykdFBKjlst64IOVIeBdS jt1w== X-Gm-Message-State: AOJu0Yz07d+iUIfoD8qe06M5sdiL4rILu9voT+W3mNGdL0Bkp7Gke2lU 3briLkbjpZKWp8FggY0TlgpILurCKeFcWV/Ixixs/afPaplnrZ2d X-Google-Smtp-Source: AGHT+IHLFM9iwS47A9Aq3ZApklMXcVHFFZTZDyaIHedKypbxU1iany+FGwhoMbdCLMpjF7fuvikyZQ== X-Received: by 2002:a05:6a20:1587:b0:1aa:a6dc:38ca with SMTP id adf61e73a8af0-1b2b6f81abcmr561850637.16.1717525843823; Tue, 04 Jun 2024 11:30:43 -0700 (PDT) Received: from smtpclient.apple ([208.28.126.37]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2c1a777f7d8sm10171194a91.31.2024.06.04.11.30.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 04 Jun 2024 11:30:43 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Teja Jakkidi Mime-Version: 1.0 (1.0) Subject: Re: pg_dump and restore without indexes Date: Tue, 4 Jun 2024 11:30:32 -0700 Message-Id: References: <8fbe6cf1-99b8-4af2-a147-acd90cd21907@ewie.name> Cc: pgsql-admin In-Reply-To: <8fbe6cf1-99b8-4af2-a147-acd90cd21907@ewie.name> To: Erik Wienhold X-Mailer: iPhone Mail (21F90) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thank you for your inputs, Erik. Regards, J. Teja. > On Jun 4, 2024, at 11:27=E2=80=AFAM, Erik Wienhold wrote:= >=20 > =EF=BB=BFOn 2024-06-04 19:58 +0200, Teja Jakkidi wrote: >> Also, is there a way we can remap schema or table during restore like >> how we have an option to remap in Oracle? >=20 > Not in pg_dump or pg_restore. Maybe some third-party tool, but I don't > know. >=20 > I had to do this in the past and just renamed the schemas after > restoring into a new database. Using a find-and-replace on the SQL dump > might also work (maybe with a clever regexp) but it's not foolproof if > the search matches false-positives in data segments or string literals. >=20 > -- > Erik