Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mj4be-0002pT-Fy for pgsql-admin@arkaria.postgresql.org; Fri, 05 Nov 2021 19:10:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mj4bc-0003ZT-Ro for pgsql-admin@arkaria.postgresql.org; Fri, 05 Nov 2021 19:10:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mj4bc-0003ZJ-GB for pgsql-admin@lists.postgresql.org; Fri, 05 Nov 2021 19:10:28 +0000 Received: from mail-qv1-xf31.google.com ([2607:f8b0:4864:20::f31]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mj4bZ-0007c5-Qi for pgsql-admin@lists.postgresql.org; Fri, 05 Nov 2021 19:10:28 +0000 Received: by mail-qv1-xf31.google.com with SMTP id s9so7895420qvk.12 for ; Fri, 05 Nov 2021 12:10:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=KZhGe6Ttq47jPbZw0BOzYcgunbJcdiu7nMtcQcyKDSQ=; b=HUuxvJ/PwtwtgACOdDaoRz7xeLQzm46zWlYn7NgEUtlf1V9koR27Ys7f6o2pDPfPZu EooGAImVnLWOIKKCQISO65a+cPKcQnqmjLx6Az23bmmhrph6U4k660ytDzA145Vbn0jW YNgOaTJiUPHtYD8vDSP0MQ6jPviT+EvC5dIPVKKFrT7ZBHImPZoV9/W6Axv3QDLIzsmz SUDiVyw5tCiIqZd2XOH3f8JjwR2kCb17oYOClv+XYSzKOBBWOwbj3iQySjvX+qQOfALY XwpPAE7QNDGPqV0+NRX9BKw22XsCCaozuX45A/YGuhOk8bYLGG1f9Tzsv9T51mWXt9iM 2tzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=KZhGe6Ttq47jPbZw0BOzYcgunbJcdiu7nMtcQcyKDSQ=; b=8AeYu/YjyBU1p8JGG0J+fn0RiwfekBkvJCQSeoMx07BUrV4+nkUJCPGunMs+1suLzN TYt5Cksok+vSDZR7j0f9uFMRhv4P6PF2cSO/OLLL4k4QSBk7YiysMg17HdFpJrgFpe3P 1UJ0NCjbgz9JNsRJ6v4ZrfcrSYXHCbyFFNwc+REfbPOsdBlmGWG9z2/q6+SL2hqxnAM7 NUC2YDjwNkFK4aqGW2FX5ncjWOC7yjdNiJCdcjTUBzqsktbkzdA0Xu6/qTyp+Ppu7jVj JFVj8+4C6G+6KtT1bbkK23SEZuDT4LbfbRFSD3qgtqq00enX/BMFM0IgLrR1YwXAjtN9 NnzQ== X-Gm-Message-State: AOAM532hjnZbN/EKhLmL1hfn1nKFcGPgeOUTwN7EQHnduxJN56Z/MO/x mF+FbNwshIAYKxh7VZCTvVtypLhydCY= X-Google-Smtp-Source: ABdhPJwAZAaif1FjrhOqQmczeaYqEMpMmplpIQDX7H1Vh8MRszP7q3HtmO6ZZpqR+7Th6feNUiswQw== X-Received: by 2002:a05:6214:d0e:: with SMTP id 14mr1105019qvh.26.1636139422893; Fri, 05 Nov 2021 12:10:22 -0700 (PDT) Received: from [192.168.254.67] (h0.171.29.71.dynamic.ip.windstream.net. [71.29.171.0]) by smtp.gmail.com with ESMTPSA id 17sm6280531qtw.16.2021.11.05.12.10.22 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 05 Nov 2021 12:10:22 -0700 (PDT) To: pgsql-admin@lists.postgresql.org From: John Scalia Subject: pg_dump weirdness Message-ID: <492eb0ca-d43e-e732-61bd-17293fff431a@gmail.com> Date: Fri, 5 Nov 2021 15:10:21 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I ran a pg_dump for a colleague, as he needs to move some data into a new database. I ran the command as: pg_dump -h original_server -t original_schema.table_name -U user -W dbname > table_name.sql after the dump was completed with no errors, I went into the target instance, and truncated the target table. I also had to do a sed operation to change the schema name in the dump file for the schema in the target. I verified that sed properly modified the file. Now, after all this, I used: psql -h target_server -U user newdbname < table_name.sql This loaded with a handful of warnings, like table already exists, the sequence already exists, and some privileges could not be set. After those warnings it ran for more than 1/2 hour to load the table. The problem is that after this was all done. I went back into the target instance, and checked the newly loaded table. There was nothing in it, i.e., 0 rows. The pg_dump and the output file claim the pg_dump version was 12.6, while the server it ran against was 11.9. Both instances are AWS RDS Aurora-PostgreSQL ones. Any ideas why there was no data in the table? Other than on inputting it using psql, there were no other errors. --jay