From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Erik Serrano <eserranos(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: backup to partitioned table |
Date: | 2022-11-16 16:04:16 |
Message-ID: | CAKFQuwZFApPf=Zrq2tsJ16tRoG_t-50wfPCLwiK6F3wOzZXtEw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Nov 16, 2022 at 8:56 AM Erik Serrano <eserranos(at)gmail(dot)com> wrote:
> I have a partitioned table in postgresql version 9,5 to which I select and
> it returns data perfectly, but when I want to make a backup of the table,
> it only saves the structure without records.
> It should be noted that I am not making a backup of the structure, but of
> the data or complete, but it does not back up the data anyway.
> When consulting the administrator, he informs me that it is a partitioned
> table and that it is always zero, but the data is in its "daughter" tables
> and that the select that it returns is the information that is housed in
> all its daughter tables.
>
> Now, given this, I wanted to know if there is any way to make a backup of
> the table that throws all the data from its child tables into a flat file.
>
>
I presume you are doing something with pg_dump...don't.
Use a "COPY" command (or psql \copy) to produce the CSV file instead.
pg_dump has its own ideas about how to go about producing an actual backup
when all you really want is a copy of the data. Because its idea of a
backup means having one csv file for each of the child tables in the
partition scheme.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2022-11-16 16:06:14 | Re: backup to partitioned table |
Previous Message | Erik Serrano | 2022-11-16 15:56:37 | backup to partitioned table |