Re: BUG #16732: pg_dump creates broken backups

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Zsolt Ero <zsolt(dot)ero(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #16732: pg_dump creates broken backups
Date: 2020-11-22 15:47:27
Message-ID: 20201122154727.GA10185@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2020-Nov-22, Zsolt Ero wrote:

> I get it. But then I need a separate step for the missing table's schema,
> right?

No, you don't. grep-v'ing for just TABLE DATA excludes the data, but
not the definition.

Please don't top-post.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dilip Kumar 2020-11-23 05:21:40 Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop
Previous Message Zsolt Ero 2020-11-22 14:49:15 Re: BUG #16732: pg_dump creates broken backups