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: Andrew Dunstan <andrew@dunslane.net>
Cc: Daniel Gustafsson <daniel@yesql.se>, Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, Tomas Vondra <tomas.vondra@enterprisedb.com>, Justin Pryzby <pryzby@telsasoft.com>, Dean Rasheed <dean.a.rasheed@gmail.com>, Stephen Frost <sfrost@snowman.net>, Surafel Temesgen <surafel3000@gmail.com>, vignesh C <vignesh21@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2022-07-17T06:20:47Z
Lists: pgsql-hackers

Attachments

Hi

čt 14. 7. 2022 v 6:54 odesílatel Pavel Stehule <pavel.stehule@gmail.com>
napsal:

>
>
> st 13. 7. 2022 v 22:49 odesílatel Andrew Dunstan <andrew@dunslane.net>
> napsal:
>
>>
>> On 2022-04-25 Mo 13:39, Pavel Stehule wrote:
>> > Hi
>> >
>> > fresh rebase
>> >
>> >
>>
>>
>> If we're going to do this for pg_dump's include/exclude options,
>> shouldn't we also provide an equivalent facility for pg_dumpall's
>> --exclude-database option?
>>
>>
> It has sense
>

The attached patch implements the --filter option for pg_dumpall and for
pg_restore too.

Regards

Pavel



>>

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.