Re: proposal: possibility to read dumped table's name from file
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Stephen Frost <sfrost@snowman.net>,
Tom Lane <tgl@sss.pgh.pa.us>,
Alvaro Herrera <alvherre@2ndquadrant.com>,
Pavel Stehule <pavel.stehule@gmail.com>,
Justin Pryzby <pryzby@telsasoft.com>,
Dean Rasheed <dean.a.rasheed@gmail.com>,
Surafel Temesgen <surafel3000@gmail.com>,
vignesh C <vignesh21@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2021-07-13T20:44:38Z
Lists: pgsql-hackers
> On 13 Jul 2021, at 18:14, Tomas Vondra <tomas.vondra@enterprisedb.com> wrote: > FWIW I don't understand why would they need to write parsers. It's quite common to write unit tests for VM recipes/playbooks wheen using tools like Chef etc, parsing and checking the installed/generated files is part of that. This would be one very real use case for writing a parser. > I think the case when the filter file needs to be modified is rather rare - it certainly is not what the original use case Pavel tried to address needs. (I know that customer and the filter would be generated and used for a single dump.) I'm not convinced that basing design decisions on a single customer reference who only want to use the code once is helpful. I hear what you're saying, but I think this will see more diverse use cases than what we can foresee here. -- Daniel Gustafsson https://vmware.com/
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