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: Justin Pryzby <pryzby@telsasoft.com>

Cc: Stephen Frost <sfrost@snowman.net>, Surafel Temesgen <surafel3000@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, vignesh C <vignesh21@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Daniel Gustafsson <daniel@yesql.se>

Date: 2020-11-19T19:57:01Z

Lists: pgsql-hackers

Attachments

pg_dump-filter-option-20201119-2.patch (text/x-patch) patch

>> BTW, in your most recent patch:
>> s/empty rows/empty lines/
>> unbalanced parens: "invalid option type (use [+-]"
>>
>
> should be fixed now, thank you for check
>

minor update - fixed handling of processing names with double quotes inside




>
> Regards
>
> Pavel
>
>
>
>> @cfbot: I renamed the patch so please ignore it.
>>
>> --
>> Justin
>>
>

Commits

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

Fix array subscript warnings
- 17935e1fdf0a 17.0 landed
Read include/exclude commands for dump/restore from file
- a5cf808be55b 17.0 landed
Allow records to span multiple lines in pg_hba.conf and pg_ident.conf.
- 8f8154a503c7 14.0 cited