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 1rpm7f-008Xmm-4T for pgsql-general@arkaria.postgresql.org; Thu, 28 Mar 2024 09:32:35 +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 1rpm7e-00AZwg-5l for pgsql-general@arkaria.postgresql.org; Thu, 28 Mar 2024 09:32:34 +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 1rpm7d-00AZrX-Nu for pgsql-general@lists.postgresql.org; Thu, 28 Mar 2024 09:32:33 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rpm7Z-006r7U-WC for pgsql-general@lists.postgresql.org; Thu, 28 Mar 2024 09:32:32 +0000 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-a466fc8fcccso89800466b.1 for ; Thu, 28 Mar 2024 02:32:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711618348; x=1712223148; darn=lists.postgresql.org; h=mime-version:subject:user-agent:message-id:date:to:from:from:to:cc :subject:date:message-id:reply-to; bh=lF9JING8kKRVbsUUWUam13mJKWJ5dnMR6KpCmvCosFA=; b=ICJF7eh5zHOMAbIQl2YS4YMgGK6y2p0ch6P33gA9pag1HMcWcr2Jd5EQrkpBX+PrNY 8jx+x0ijqPNzXRvb+wN9OtAVaxEUE9zvqPNyHSfu+mt58BQSoPdYwsK8ynts1/emMiME 7YZ8mNiEmrIM40hRV/GCcp3PmF9tf5XSKqWg50/bQ9Irr95rId/laa//P2Df7z2SXu0m CHK1ytynI3HGnb3S4fAYTKf34/nX/d2EcPjwifbMFIAvcjQmDZd1LzQesImlWgchka1F 2XlHoNkIK/KVCRvCztDJ0VL5V8NCy5YB6M3ZB8ADMILCKi0frunjxGQ2bdHi+jojDJbs ctng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711618348; x=1712223148; h=mime-version:subject:user-agent:message-id:date:to:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=lF9JING8kKRVbsUUWUam13mJKWJ5dnMR6KpCmvCosFA=; b=A3qNFyw7kUYrTeWhxZHcDGi347mnkMCKAXh6gizhpHkkzwQKjfg1Tk1FZzPokLjct3 9mEvvQ6dFopFGD+L6EtGFHpFlO0IhL9yoVHECCHXLrysoKW2zY8uefV3MLT62Pi1EDNn eA8xlmrz8THJEnOEPQ9G9jMIQqmEsxdJwKPbd5k9kd9N1OzPQoXiTzykJ7vQlQLaegki plnNI6Pb1A9Fjp21cD5X3avDpu2pcNv2Mbho9yZ1r2SO+FF+EZY8Tmv2I+7TX75GnG0i VuL4OwTo+wbzGrLfgvcfaBtMIkZNEx2jzBoYN0/7SoiEEuTROj9XofgdDuyvIdD58OpV d/WQ== X-Gm-Message-State: AOJu0YwuDQRotEgZAyBfBJppngwkD67xCOcSLj5VS8obcjcjhE92niMO BsQnpt6K6FwunfDsH9O4XQw7oHgLL+klfDAJlnOP4NUgJ+dN8SWORSIzrKGC X-Google-Smtp-Source: AGHT+IGQdUyz/Ax/2unxdblwaGZElYyvPqFut5Qb+dM4qVLaTX+Sn6XoliHjRIxTYIPCP43mHygExg== X-Received: by 2002:a17:906:a0d5:b0:a46:a3bc:b343 with SMTP id bh21-20020a170906a0d500b00a46a3bcb343mr1341552ejb.21.1711618347658; Thu, 28 Mar 2024 02:32:27 -0700 (PDT) Received: from [192.168.1.7] (p5b3e6b8f.dip0.t-ipconnect.de. [91.62.107.143]) by smtp.gmail.com with ESMTPSA id dc13-20020a170906c7cd00b00a4655513f0bsm531065ejb.88.2024.03.28.02.32.26 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Thu, 28 Mar 2024 02:32:27 -0700 (PDT) From: Fire Emerald To: Date: Thu, 28 Mar 2024 10:32:26 +0100 Message-ID: <18e84674c10.2815.a5aef60df33e8d2ac3d54c6545825f63@gmail.com> User-Agent: AquaMail/1.50.0 (build: 105000429) Subject: How to interpret 'depends on' errors in pg_restore? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="18e84674ef56a2e281527a6146" 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. --18e84674ef56a2e281527a6146 Content-Type: text/plain; format=flowed; charset="us-ascii" Content-Transfer-Encoding: 8bit Hello everyone, I created a database dump in postgres 'custom' format using: pg_dump -d origin --data-only -Fc > file.dump Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the output this: 5145 0 730750 TABLE subpartitions backends_y2024w03 userA ; depends on: 237 .... and so on ... Nothing was restored. The tables mentioned in the output do all exist - but in a different database, thus the "internal id's" - perhaps thats what "depends on" refers to - are in fact different but the id's should not matter, as the table names are important and they all exist. How to interpret the "depends on" errors which lead to nothing beeing imported? and is there a way to tell pg_restore to skip those depends on checks? When i created a sql dump with inserts, everything worked but these dumps are not that efficient. Best regards, Christian --18e84674ef56a2e281527a6146 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hello everyone,

I created a da= tabase dump in postgres 'custom' format using: pg_dump -d origin --data-onl= y -Fc > file.dump

The= n i did a pg_restore -d target --verbose -Fc file.dump and saw in the outpu= t this:

5145 0 730750 TA= BLE subpartitions backends_y2024w03 userA
;  &n= bsp;     depends on: 237
.... and so on ..= .

Nothing was restored. = The tables mentioned in the output do all exist - but in a different databa= se, thus the "internal id's" - perhaps thats what "depends on" refers to - = are in fact different but the id's should not matter, as the table n= ames are important and they all exist.

How to interpret the "depends on" errors which lead to nothi= ng beeing imported? and is there a way to tell pg_restore to skip those dep= ends on checks?

When i c= reated a sql dump with inserts, everything worked but these dumps are not t= hat efficient.

Best rega= rds,
Christian
--18e84674ef56a2e281527a6146--