blocks|key|354372|text|选项1:|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|354373|在Postgres容器上执行pg_dump命令：|CODE|354374|pg_dump+-U+username+-d+dbname+>+data.sql|code-block|syntax|javascript|354375|实际上，您可能只需要数据，而不需要hasura元数据或schema_migration信息。这是一个更好的“数据导出”类型命令：|354376|pg_dump+-U+username+-d+dbname+--data-only+--schema+public+>+data.sql|354377|备选方案2:|354378|如果Postgres作为Docker容器运行：|354379|#+Exec+into+the+postgres+container
$+docker+exec+-ti+<postgres-id>+--+/bin/bash
#+Run+pg_dump
root@postgres-3391217220-t7bbc:/$+pg_dump+-U+postgres+-d+postgres+--data-only+--schema+public+>+db.sql
%5ED

#+Back+on+your+local+machine,+copy+the+dump
$+docker+cp+<postgres-id>:/db.sql+db.sql|354380|entityMap^0|0|4|0|E|7|0|0|0|0|0|6|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|12|8|@$9|13|A|14|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|15|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|16|8|@]|D|@]|E|$]]|$1|P|3|Q|5|K|7|17|8|@]|D|@]|E|$L|M]]|$1|R|3|S|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|T|3|U|5|6|7|1B|8|@]|D|@]|E|$]]|$1|V|3|W|5|K|7|1C|8|@]|D|@]|E|$L|M]]|$1|X|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|Y|$]]

Option 1:

Exec a <code>pg_dump</code> command on your Postgres container:

<pre><code>pg_dump -U username -d dbname &gt; data.sql
</code></pre>

In practice, you probably only want the data and not the hasura metadata or schema_migration information. This is a better 'data export' type command: 

<pre><code>pg_dump -U username -d dbname --data-only --schema public &gt; data.sql
</code></pre>

Option 2:

If Postgres is running as a Docker container:

<pre><code># Exec into the postgres container
$ docker exec -ti &lt;postgres-id&gt; -- /bin/bash
# Run pg_dump
root@postgres-3391217220-t7bbc:/$ pg_dump -U postgres -d postgres --data-only --schema public &gt; db.sql
^D

# Back on your local machine, copy the dump
$ docker cp &lt;postgres-id&gt;:/db.sql db.sql
</code></pre>

blocks|key|1625639|text|Hasura有一个默认启用的pgdump+API命令。以下是文档：https://docs.hasura.io/1.0/graphql/manual/api-reference/pgdump.html|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1625640|文档目前缺少的就是一个例子。下面是一个示例，用于转储Hasura数据，但不是模式(它来自迁移)，以便将其导入本地托管的dev+hasura+(假设您使用了hasura-admin-secret，或者根据需要用其他标头替换)：|1625641|HASURA_SECRET=som3_Secr3t_Her3
curl+-d+'{"-Fc",+"opts":+["--data-only"]}'+-H+"x-hasura-admin-secret:+$HASURA_SECRET"+https://your-host-url.com/v1alpha1/pg_dump+>+dumpfile|code-block|syntax|javascript|1625642|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.hasura.io/1.0/graphql/manual/api-reference/pgdump.html^0|E|6|X|1V|0|0|25|J|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|13|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

Hasura has a <code>pgdump</code> API command, enabled by default. Here are the docs: <a href="https://docs.hasura.io/1.0/graphql/manual/api-reference/pgdump.html" rel="noreferrer">https://docs.hasura.io/1.0/graphql/manual/api-reference/pgdump.html</a>

What the docs currently lack is an example. Here's an example I use to dump the Hasura data, but not the schema (which comes from migrations) in order to import it into my locally hosted dev hasura (insert your own <code>hasura-admin-secret</code>, assuming you use one, or replace with other headers as needed):

<pre class="lang-sh prettyprint-override"><code>HASURA_SECRET=som3_Secr3t_Her3
curl -d '{"-Fc", "opts": ["--data-only"]}' -H "x-hasura-admin-secret: $HASURA_SECRET" https://your-host-url.com/v1alpha1/pg_dump &gt; dumpfile
</code></pre>

blocks|key|813778|text|2022:+Hasura诉2.1.1|type|unstyled|depth|inlineStyleRanges|entityRanges|data|813779|要从postgres/Hasura实例导出数据，我们需要使用Postman或curl客户端对隐藏的Hasura端点/v1alpha1/pg_dump发出http+POST请求，如下所示：|offset|length|style|CODE|813780|http://<your-hasura-host>/v1alpha1/pg_dump|813781|一个示例curl命令：|813782|curl+-d+'{"opts":+["-a",+"-O",+"-x",+"--inserts",+"--exclude-schema=hdb_catalog"],+"clean_output":+true,+"source":+"default"}'+-H+"x-hasura-admin-secret:your-admin-secret-here"+http://your-hasura-host/v1alpha1/pg_dump|813783|上面添加了一个标头来指定Hasura管理秘密：|813784|x-hasura-admin-secret:<your+admin+secret+key>|code-block|syntax|javascript|813785|-d为pg_dump+&Hasura的端点处理程序添加了一个带有选项("opts")的JSON主体：|813786|{
++"opts":+["-a",+"-O",+"-x",+"--inserts",+"--exclude-schema=hdb_catalog"],
++"clean_output":+true,
++"source":+"default"
}|813787|以上pg_dump选项("opts")如下：|813788|-a：仅数据，而不是模式|unordered-list-item|813789|-O：没有所有权声明|813790|-x：没有访问特权语句|813791|--inserts：使用SQL语句，而不是psql命令|813792|--exclude-schema=hdb_catalog：没有与Hasura迁移/元数据相关的记录，只有我们的数据|813793|clean_output键/值从转储输出中移除一组SET语句和注释，如：|813794|--
--+PostgreSQL+database+dump
--

--+Dumped+from+database+version+12.4+(Debian+12.4-1.pgdg100%2B1)
--+Dumped+by+pg_dump+version+13.4+(Debian+13.4-4.pgdg100%2B1)

SET+statement_timeout+=+0;
SET+lock_timeout+=+0;
SET+idle_in_transaction_session_timeout+=+0;
SET+client_encoding+=+'UTF8';
SET+standard_conforming_strings+=+on;
SELECT+pg_catalog.set_config('search_path',+'',+false);
SET+check_function_bodies+=+false;
SET+xmloption+=+content;
SET+client_min_messages+=+warning;
SET+row_security+=+off;|813795|source指定要转储的数据库的名称。通常情况下，这将是default，除非您在设置Hasura时更改它。|813796|您得到的输出应该是一个SET语句，后面是一组INSERT+INTO语句。|813797|这可以直接复制/粘贴到Hasura控制台的data+>+SQL选项卡中，并运行以导入转储数据。|813798|参考资料/有用链接|813799|https://www.postgresql.org/docs/13/app-pgdump.html|813800|https://hasura.io/docs/latest/graphql/core/api-reference/pgdump.html|813801|https://hasura.io/docs/latest/graphql/core/migrations/advanced/seed-data-migration.html|813802|备注|813803|我需要pg_dump作为种子数据在应用Hasura迁移时使用，从旧实例到新的Hasura实例。但是(在我的例子中)，Hasura对旧实例的初始迁移输出包括一组hdb_catalog+create语句，这将确保在将迁移应用到新的Hasura实例时失败。(+hdb_catalog模式/表已经存在于新的/新的Hasura安装中)|813804|为了纠正这一点，我需要对旧实例进行复位偏移并重新执行迁移命令(如前面的链接所示)。这个新的迁移输出不包括hdb_catalog模式，可以将OK应用于新的Hasura实例。|813805|然后，我可以在新实例的Hasura选项卡/窗口中运行pg_dump输出来重新填充我的表。|813806|entityMap|0|LINK|mutability|MUTABLE|url|1|2|3|https://hasura.io/docs/latest/graphql/core/migrations/migrations-setup.html#step-7-apply-the-migrations-and-metadata-on-another-instance-of-the-graphql-engine|4|https://hasura.io/docs/latest/graphql/core/migrations/advanced/resetting-migrations.html^0|0|1L|H|0|0|16|0|4|4|0|0|61|0|0|0|0|2|0|0|0|0|2|0|0|2|0|0|2|0|0|9|0|0|S|0|0|C|0|0|0|6|S|7|0|B|3|M|B|0|0|0|0|1E|0|0|0|1W|1|0|0|2F|2|0|0|27|B|H|A|3|0|H|4|4|0|0^^$0|@$1|2|3|4|5|6|7|2E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2F|8|@$D|2G|E|2H|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|2I|8|@$D|2J|E|2K|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|2L|8|@$D|2M|E|2N|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|2O|8|@$D|2P|E|2Q|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|2R|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|2S|8|@]|9|@]|A|$S|T]]|$1|U|3|V|5|6|7|2T|8|@$D|2U|E|2V|F|G]]|9|@]|A|$]]|$1|W|3|X|5|R|7|2W|8|@]|9|@]|A|$S|T]]|$1|Y|3|Z|5|6|7|2X|8|@]|9|@]|A|$]]|$1|10|3|11|5|12|7|2Y|8|@$D|2Z|E|30|F|G]]|9|@]|A|$]]|$1|13|3|14|5|12|7|31|8|@$D|32|E|33|F|G]]|9|@]|A|$]]|$1|15|3|16|5|12|7|34|8|@$D|35|E|36|F|G]]|9|@]|A|$]]|$1|17|3|18|5|12|7|37|8|@$D|38|E|39|F|G]]|9|@]|A|$]]|$1|19|3|1A|5|12|7|3A|8|@$D|3B|E|3C|F|G]]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|3D|8|@$D|3E|E|3F|F|G]]|9|@]|A|$]]|$1|1D|3|1E|5|R|7|3G|8|@]|9|@]|A|$S|T]]|$1|1F|3|1G|5|6|7|3H|8|@$D|3I|E|3J|F|G]|$D|3K|E|3L|F|G]]|9|@]|A|$]]|$1|1H|3|1I|5|6|7|3M|8|@$D|3N|E|3O|F|G]|$D|3P|E|3Q|F|G]]|9|@]|A|$]]|$1|1J|3|1K|5|6|7|3R|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|6|7|3S|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|12|7|3T|8|@]|9|@$D|3U|E|3V|1|3W]]|A|$]]|$1|1P|3|1Q|5|12|7|3X|8|@]|9|@$D|3Y|E|3Z|1|40]]|A|$]]|$1|1R|3|1S|5|12|7|41|8|@]|9|@$D|42|E|43|1|44]]|A|$]]|$1|1T|3|1U|5|6|7|45|8|@]|9|@]|A|$]]|$1|1V|3|1W|5|6|7|46|8|@$D|47|E|48|F|G]]|9|@$D|49|E|4A|1|4B]]|A|$]]|$1|1X|3|1Y|5|6|7|4C|8|@]|9|@$D|4D|E|4E|1|4F]]|A|$]]|$1|1Z|3|20|5|6|7|4G|8|@]|9|@]|A|$]]|$1|21|3|-4|5|6|7|4H|8|@]|9|@]|A|$]]]|22|$23|$5|24|25|26|A|$27|1O]]|28|$5|24|25|26|A|$27|1Q]]|29|$5|24|25|26|A|$27|1S]]|2A|$5|24|25|26|A|$27|2B]]|2C|$5|24|25|26|A|$27|2D]]]]

<h1>2022: Hasura v.2.1.1</h1>
To export data from a postgres/Hasura instance, we need to use Postman or a curl client to make a http POST request against a hidden Hasura endpoint <code>/v1alpha1/pg_dump</code> like so:
<code>http://&lt;your-hasura-host&gt;/v1alpha1/pg_dump</code>
An example <code>curl</code> command:
<code>curl -d '{&quot;opts&quot;: [&quot;-a&quot;, &quot;-O&quot;, &quot;-x&quot;, &quot;--inserts&quot;, &quot;--exclude-schema=hdb_catalog&quot;], &quot;clean_output&quot;: true, &quot;source&quot;: &quot;default&quot;}' -H &quot;x-hasura-admin-secret:your-admin-secret-here&quot; http://your-hasura-host/v1alpha1/pg_dump</code>
The above adds a header to specify your Hasura admin secret:
<pre><code>x-hasura-admin-secret:&lt;your admin secret key&gt;
</code></pre>
And the <code>-d</code> adds a JSON body with options (&quot;opts&quot;) for pg_dump &amp; Hasura's endpoint handler:
<pre><code>{
 &quot;opts&quot;: [&quot;-a&quot;, &quot;-O&quot;, &quot;-x&quot;, &quot;--inserts&quot;, &quot;--exclude-schema=hdb_catalog&quot;],
 &quot;clean_output&quot;: true,
 &quot;source&quot;: &quot;default&quot;
}
</code></pre>
The pg_dump options (&quot;opts&quot;) above are:
<ul>
<li><code>-a</code>: data-only, not schemas</li>
<li><code>-O</code>: no ownership statements</li>
<li><code>-x</code>: no access privilege statements</li>
<li><code>--inserts</code>: use SQL statements, not psql commands</li>
<li><code>--exclude-schema=hdb_catalog</code>: no Hasura migration/metadata related records, just our data</li>
</ul>
The <code>clean_output</code> key/value removes a bunch of SET statements &amp; comments from the dump output such as:
<pre><code>--
-- PostgreSQL database dump
--

-- Dumped from database version 12.4 (Debian 12.4-1.pgdg100+1)
-- Dumped by pg_dump version 13.4 (Debian 13.4-4.pgdg100+1)

SET statement_timeout = 0;
SET lock_timeout = 0;
SET idle_in_transaction_session_timeout = 0;
SET client_encoding = 'UTF8';
SET standard_conforming_strings = on;
SELECT pg_catalog.set_config('search_path', '', false);
SET check_function_bodies = false;
SET xmloption = content;
SET client_min_messages = warning;
SET row_security = off;
</code></pre>
<code>source</code> specifies the name of the database to dump. Usually this would be <code>default</code> unless you changed it when setting up Hasura.
The output you get should be a single <code>SET</code> statement followed by a bunch of <code>INSERT INTO</code> statements.
This can be copy/pasted directly into Hasura Console's Data &gt; SQL tab and run to import the dumped data.
<h3>References/Useful Links</h3>
<ul>
<li><a href="https://www.postgresql.org/docs/13/app-pgdump.html" rel="noreferrer">https://www.postgresql.org/docs/13/app-pgdump.html</a></li>
<li><a href="https://hasura.io/docs/latest/graphql/core/api-reference/pgdump.html" rel="noreferrer">https://hasura.io/docs/latest/graphql/core/api-reference/pgdump.html</a></li>
<li><a href="https://hasura.io/docs/latest/graphql/core/migrations/advanced/seed-data-migration.html" rel="noreferrer">https://hasura.io/docs/latest/graphql/core/migrations/advanced/seed-data-migration.html</a></li>
</ul>
<h4>Notes</h4>
I needed the pg_dump as seed data to use when <a href="https://hasura.io/docs/latest/graphql/core/migrations/migrations-setup.html#step-7-apply-the-migrations-and-metadata-on-another-instance-of-the-graphql-engine" rel="noreferrer">applying a Hasura migration</a>, from an old instance to a new Hasura instance. But (in my case) the initial migration output by Hasura CLI on the old instance included a bunch of <code>hdb_catalog</code> create schema statements, which would ensure failure when applying the migration onto a new Hasura instance. (The hdb_catalog schema/tables already exist on a new/fresh Hasura install)
To correct this, I needed to <a href="https://hasura.io/docs/latest/graphql/core/migrations/advanced/resetting-migrations.html" rel="noreferrer">reset migrations</a> on the old instance and redo the migration commands (as shown in the aforementioned link). This new migration output didn't include the hdb_catalog schema, and could be applied OK to the new Hasura instance.
I could then just run the pg_dump output in Hasura Console SQL tab/window on the new instance to repopulate my tables.

I want to take a pg_dump of my data from HasuraDB to my local machine. What is the recommended way to do this ?

How do I take a postgres data backup on Hasura

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想把数据的pg_dump从HasuraDB带到我的本地机器。建议的方法是什么？

问如何对Hasura进行postgres数据备份
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何对Hasura进行postgres数据备份EN