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 1qvLeH-004ene-9x for pgsql-admin@arkaria.postgresql.org; Tue, 24 Oct 2023 17:57:01 +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 1qvLeE-00B4up-Kg for pgsql-admin@arkaria.postgresql.org; Tue, 24 Oct 2023 17:56:59 +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 1qvLeE-00B4ue-6w for pgsql-admin@lists.postgresql.org; Tue, 24 Oct 2023 17:56:58 +0000 Received: from mail-yw1-x1136.google.com ([2607:f8b0:4864:20::1136]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qvLe7-002VAp-ST for pgsql-admin@lists.postgresql.org; Tue, 24 Oct 2023 17:56:58 +0000 Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-5a7a80a96dbso339557b3.0 for ; Tue, 24 Oct 2023 10:56:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698170210; x=1698775010; darn=lists.postgresql.org; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=7xq//c+Cjr9OnPx4SoYjex4/Ry8CRYIaHnSV3jR6zGs=; b=LHsYW58zXyNlqk8c6pOBNgKsnjyU1FX/wQWS5lZuoq9zGoPUjF5xTC34V+HJxAPg2Q U9f4rqS0nIzj4rxflD55uSHO08QIQA2DFAPKmhlks2sAyA0+k6FLORu5aEzrrxWaYxVQ 3q4/pJU0YEGJo6NU2EhSSyNFhaMLBkGUkyvDVXWQdZtUIh18bQVqoqENLgo1Qkr5BClM DdeXINejJf9rjtYBsChn7jDBo+Fv0r+r1GUqNm69vhIud6n/GzCJeKa1NfTBDP2RPTWl 6CXtLYRFBRHpi/9jX6VC40tzN26rBwzLD6W9l3eDD+PZliamS1Y2EGXdUPmA+2nTOYbr 2Iiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698170210; x=1698775010; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=7xq//c+Cjr9OnPx4SoYjex4/Ry8CRYIaHnSV3jR6zGs=; b=a0BfnBoK0RGkQhkrknQ+g9nlOocyCWPeVRAXMezJX/UJvdDYdiwg/INOJ520nO6Hc5 Rpy2C6tqYOl7F5pai5QKbHu5FqytJ78YDu3JxDxITWBKnMxoHdt3ZTOGqkjdzy0PKW6X S677VX15agJKvT0ylWGxjh9iEc+k2Lr9adz2ziI9rMLKa+vTcBENBg63lieIhEfHrUrm /erZU8zIebRoE6UgApch2czrKnb6ePhodD8aJbif0QL/a0BEX8hrzJfREl/Z+nlWo86s OMGdExJxc69vbaCBq5YanCBglY5u3Z/VU7vnf9Q1zjFhgHrKo0oE9HQhwCrN+HElERqx 7oBw== X-Gm-Message-State: AOJu0Yx2GJiUMeK9bpVDmWSUbIGa2SyZmsZhCMJF8qVBAlrsQj2xBYFu zz0v83A2GlXnriOMFerGUUI6CUrz5Qo= X-Google-Smtp-Source: AGHT+IHL/G0hp4MeYL0EZXH26Qyttr07mmCkXG5kF2veNyrEBW5wqGzOy53/WsIxmY/ShMKa4W2YeQ== X-Received: by 2002:a81:49d2:0:b0:5a8:19bf:87db with SMTP id w201-20020a8149d2000000b005a819bf87dbmr12252512ywa.25.1698170209775; Tue, 24 Oct 2023 10:56:49 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:990b:551:8028:180e? ([2600:1700:bd2c:b810:990b:551:8028:180e]) by smtp.googlemail.com with ESMTPSA id y10-20020a81a10a000000b005a7cc149e3asm4250969ywg.2.2023.10.24.10.56.49 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 24 Oct 2023 10:56:49 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------7C0Xl55RNfbZORpCCHJLT0ls" Message-ID: Date: Tue, 24 Oct 2023 12:56:48 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pg_restore is not working Content-Language: en-US To: "pgsql-admin@lists.postgresql.org" References: <0100018b62722391-65a890bf-5d6b-415f-8831-bf8ae2a09fde-000000@email.amazonses.com> From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------7C0Xl55RNfbZORpCCHJLT0ls Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 10/24/23 12:24, M Sarwar wrote: > Hi Ron, > > I did try using -Fc clause. pg_dump is running fine but pg_restore is > having the same issue. > I tried once again now after seeing your email and getting the same scenario. > > Pg_Dump:- > > PS H:\> pg_dump -Fc -v -h*/sharded/*-U db_sarwar -d NGBRDVDB -t > 'bronxdev.errors' -f > C:\Mohammed\Work\NGC\Apps\Bronx\Backups\Dumps\data\backup_Dev_Bronxdev-Errors_20231024-6.DUMP > > Password: > > Pg_dump ran fine. > > Pg_Restore:- > > PS H:\> pg_restore -v -h*/sharded/* -U db_sarwar -d bronxdb1 -t > 'bronxdev.errors' > C:\Mohammed\Work\NGC\Apps\Bronx\Backups\Dumps\data\backup_Dev_Bronxdev-Errors_20231024-6.DUMP > > pg_restore: connecting to database for restore > > Password: > > pg_restore: implied data-only restore > > PS H:\> pg_restore -Fc -v -h*/sharded/* -U db_sarwar -d bronxdb1 -t > 'bronxdev.errors' > C:\Mohammed\Work\NGC\Apps\Bronx\Backups\Dumps\data\backup_Dev_Bronxdev-Errors_20231024-6.DUMP > > pg_restore: connecting to database for restore > > Password: > > pg_restore: implied data-only restore > > PS H:\> > > It has no errors but it did not restore the data. > This works for me.  I just tested it.  You'll have to convert from bash to Windows. SrcHost=somehost DescHost=anotherhost SrcDir=/var/lib/pgsql/backups/test SrcDB=somedb DestDB=anotherdb Tbl=public.job pg_dump --host=$SrcHost -Fc -t $Tbl -v -d ${SrcDB} -f $SrcDir/${Tbl}.dump pg_restore --host=$DestHost -v -d ${DestDB} ${SrcDir}/${Tbl}.dump > Thanks, > Sarwar > > ---------------------------------------------------------------------------- > *From:* Ron > *Sent:* Tuesday, October 24, 2023 1:08 PM > *To:* pgsql-admin@lists.postgresql.org > *Subject:* Re: pg_restore is not working > On 10/24/23 11:43, M Sarwar wrote: >> >> Hi, >> >> Restore is having no errors but it is not restoring any data. >> I have used the below command pg_dump >> pg_dump -F t -v -h bronxdb1.c52p1yyyjuib.us-xxx-west-1.rds.amazonaws.com >> -U db_sarwar -d NGBRDVDB -t 'bronxdev.errors' -f >> C:\Mohammed\Work\NGC\Apps\Bronx\Backups\Dumps\data\backup_Dev_Bronxdev-Errors_20231024-5.DUMP >> > > Why "-Ft" instead of "-Fc" for a .dump file? > >> I am using the below command for the restore. >> >> PS H:\> pg_restore -F t -v -h >> bronxdb1.c52p1fyyyuib.us-xxx-west-1.rds.amazonaws.com -U db_sarwar -d >> bronxdb1 -t 'bronxdev.errors' >> C:\Mohammed\Work\NGC\Apps\Bronx\Backups\Dumps\data\backup_Dev_Bronxdev-Errors_20231024-5.DUMP >> pg_restore: connecting to database for restore >> Password: >> pg_restore: implied data-only restore >> PS H:\> >> >> Thanks, >> Sarwar >> > > -- > Born in Arizona, moved to Babylonia. -- Born in Arizona, moved to Babylonia. --------------7C0Xl55RNfbZORpCCHJLT0ls Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 10/24/23 12:24, M Sarwar wrote:
Hi Ron,

I did try using -Fc clause. pg_dump is running fine but pg_restore is having the same issue.
I tried once again now after seeing your email and getting the same scenario.

Pg_Dump:-

PS H:\> pg_dump -Fc -v -h sharded -U db_sarwar -d NGBRDVDB -t 'bronxdev.errors' -f C:\Mohammed\Work\NGC\Apps\Bronx\Backups\Dumps\data\backup_Dev_Bronxdev-Errors_20231024-6.DUMP

Password:

 

Pg_dump ran fine.

 

Pg_Restore:-

 

PS H:\> pg_restore -v -h sharded  -U db_sarwar -d bronxdb1 -t 'bronxdev.errors' C:\Mohammed\Work\NGC\Apps\Bronx\Backups\Dumps\data\backup_Dev_Bronxdev-Errors_20231024-6.DUMP

pg_restore: connecting to database for restore

Password:

pg_restore: implied data-only restore

PS H:\> pg_restore -Fc -v -h sharded  -U db_sarwar -d bronxdb1 -t 'bronxdev.errors' C:\Mohammed\Work\NGC\Apps\Bronx\Backups\Dumps\data\backup_Dev_Bronxdev-Errors_20231024-6.DUMP

pg_restore: connecting to database for restore

Password:

pg_restore: implied data-only restore

PS H:\>

 

It has no errors but it did not restore the data.


This works for me.  I just tested it.  You'll have to convert from bash to Windows.

SrcHost=somehost
DescHost=anotherhost

SrcDir=/var/lib/pgsql/backups/test

SrcDB=somedb

DestDB=anotherdb

Tbl=public.job

pg_dump --host=$SrcHost -Fc -t $Tbl -v -d ${SrcDB} -f $SrcDir/${Tbl}.dump

pg_restore --host=$DestHost -v -d ${DestDB} ${SrcDir}/${Tbl}.dump

Thanks,
Sarwar

From: Ron <ronljohnsonjr@gmail.com>
Sent: Tuesday, October 24, 2023 1:08 PM
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: pg_restore is not working
 
On 10/24/23 11:43, M Sarwar wrote:
 

Hi,

Restore is having no errors but it is not restoring any data.
I have used the below command pg_dump
pg_dump -F t -v -h bronxdb1.c52p1yyyjuib.us-xxx-west-1.rds.amazonaws.com -U db_sarwar -d NGBRDVDB -t 'bronxdev.errors' -f C:\Mohammed\Work\NGC\Apps\Bronx\Backups\Dumps\data\backup_Dev_Bronxdev-Errors_20231024-5.DUMP


Why "-Ft" instead of "-Fc" for a .dump file?

I am using the below command for the restore.

PS H:\> pg_restore -F t -v -h bronxdb1.c52p1fyyyuib.us-xxx-west-1.rds.amazonaws.com -U db_sarwar -d bronxdb1 -t 'bronxdev.errors' C:\Mohammed\Work\NGC\Apps\Bronx\Backups\Dumps\data\backup_Dev_Bronxdev-Errors_20231024-5.DUMP
pg_restore: connecting to database for restore
Password:
pg_restore: implied data-only restore
PS H:\>

Thanks,
Sarwar

 


--
Born in Arizona, moved to Babylonia.

--
Born in Arizona, moved to Babylonia.
--------------7C0Xl55RNfbZORpCCHJLT0ls--