Re: proposal: possibility to read dumped table's name from file

Pavel Stehule <pavel.stehule@gmail.com>

From: Pavel Stehule <pavel.stehule@gmail.com>
To: Surafel Temesgen <surafel3000@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, vignesh C <vignesh21@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2020-09-11T08:50:01Z
Lists: pgsql-hackers
Hi

po 7. 9. 2020 v 14:14 odesílatel Surafel Temesgen <surafel3000@gmail.com>
napsal:

> Hi Pavel
>
> On Fri, Sep 4, 2020 at 6:22 AM Pavel Stehule <pavel.stehule@gmail.com>
> wrote:
>
>>
>> Here is updated patch for pg_dump
>>
>>
> pg_dumpall also has –exclude-database=pattern and –no-comments option
> doesn't that qualify it to benefits from this feature? And please add a
> test case for this option
>

This patch is related to pg_dump (in this moment), so pg_dumpall options
are out of scope.

I am not sure if pg_dumpall needs this functionality - maybe, but I can use
bash or some similar for implementation of this feature. There is no
requirement to do it all necessary work under one transaction, one snapshot.

For pg_dump can be used different format, because it uses different
granularity.  Some like "{+/-} dbname"

"--no-comments" is a global parameter without arguments. I don't understand
how this parameter can be related to this feature?

I am working on regress tests.

Regards

Pavel


> regards
>
> Surafel
>
>

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix array subscript warnings

  2. Read include/exclude commands for dump/restore from file

  3. Allow records to span multiple lines in pg_hba.conf and pg_ident.conf.