From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Surafel Temesgen <surafel3000(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: possibility to read dumped table's name from file |
Date: | 2021-07-13 20:44:38 |
Message-ID: | 0CDB1A7D-F3FB-4689-B452-9E95A8DC6B8C@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 13 Jul 2021, at 18:14, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)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/
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2021-07-13 20:55:35 | Re: proposal: possibility to read dumped table's name from file |
Previous Message | Tom Lane | 2021-07-13 20:41:01 | Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails |