Re: parse/analyze API refactoring

Поиск
Список
Период
Сортировка
Искать
От
Bossart, Nathan
Тема
Re: parse/analyze API refactoring
Дата
Msg-id
E684B0DB-2A23-4E02-80F1-C54D3856E0E6@amazon.com
Ответ на
Список
Дерево обсуждения
parse/analyze API refactoring Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: parse/analyze API refactoring "Bossart, Nathan" <bossartn@amazon.com>
Re: parse/analyze API refactoring Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: parse/analyze API refactoring Nathan Bossart <nathandbossart@gmail.com>
Re: parse/analyze API refactoring Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: parse/analyze API refactoring Nathan Bossart <nathandbossart@gmail.com>
On 12/28/21, 8:25 AM, "Peter Eisentraut"  wrote:
> (The "withcb" naming maybe isn't great; better ideas welcome.)

FWIW I immediately understood that this meant "with callback," so it
might be okay.

> Not included in this patch set, but food for further thought:  The
> pg_analyze_and_rewrite_*() functions aren't all that useful (anymore).
> One might as well write
>
>      pg_rewrite_query(parse_analyze_xxx(...))

I had a similar thought while reading through the patches.  If further
deduplication isn't too much trouble, I'd vote for that.

Nathan

В списке pgsql-hackers по дате отправления
От: Thomas Munro
Дата:
От: Tatsuo Ishii
Дата:
FAQ