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

Erik Rijkers <er@xs4all.nl>

From: Erik Rijkers <er@xs4all.nl>
To: Daniel Gustafsson <daniel@yesql.se>, Andrew Dunstan <andrew@dunslane.net>
Cc: John Naylor <john.naylor@enterprisedb.com>, Julien Rouhaud <rjuju123@gmail.com>, Pavel Stehule <pavel.stehule@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, Tomas Vondra <tomas.vondra@enterprisedb.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-09-12T14:18:41Z
Lists: pgsql-hackers

Op 12-09-2022 om 16:00 schreef Erik Rijkers:
> Op 12-09-2022 om 09:58 schreef Daniel Gustafsson:
>>> On 9 Sep 2022, at 11:00, Andrew Dunstan <andrew@dunslane.net> wrote:
>>>
>>>> On Sep 9, 2022, at 5:53 PM, John Naylor 
>>>> <john.naylor@enterprisedb.com> wrote:
> 
>>>> [v4-0001-Add-include-exclude-filtering-via-file-in-pg_dump.patch]
> 
> I noticed that pg_restore --filter cannot, or at last not always, be 
> used with the same filter-file that was used to produce a dump with 
> pg_dump --filter.
> 
> Is that as designed?  It seems a bit counterintuitive.  It'd be nice if 
> that could be fixed.  Admittedly, the 'same' problem in pg_restore -t, 
> also less than ideal.
> 
> (A messy bashdemo below)

I hope the issue is still clear, even though in the bash I sent, I 
messed up the dumpfile name (i.e., in the bash that I sent the pg_dump 
creates another dump name than what is given to pg_restore. They should 
use the same dumpname, obviously)

> 
> thanks,
> 
> Erik Rijkers



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.