Re: automating RangeTblEntry node support
От
Peter Eisentraut
Тема
Re: automating RangeTblEntry node support
Дата
Msg-id
859d6155-e361-4a05-8db3-4aa1f007ff28@eisentraut.org
Ответ на
automating RangeTblEntry node support (Peter Eisentraut)
Список
Дерево обсуждения
automating RangeTblEntry node support Peter Eisentraut <peter@eisentraut.org>
Re: automating RangeTblEntry node support Peter Eisentraut <peter@eisentraut.org>
Re: automating RangeTblEntry node support Paul Jungwirth <pj@illuminatedcomputing.com>
Re: automating RangeTblEntry node support Matthias van de Meent <boekewurm+postgres@gmail.com>
Re: automating RangeTblEntry node support Peter Eisentraut <peter@eisentraut.org>
Re: automating RangeTblEntry node support Peter Eisentraut <peter@eisentraut.org>
Re: automating RangeTblEntry node support Andrew Dunstan <andrew@dunslane.net>
Re: automating RangeTblEntry node support Peter Eisentraut <peter@eisentraut.org>
Re: automating RangeTblEntry node support Matthias van de Meent <boekewurm+postgres@gmail.com>
On 06.12.23 21:02, Peter Eisentraut wrote: > I have been looking into what it would take to get rid of the > custom_read_write and custom_query_jumble for the RangeTblEntry node > type. This is one of the larger and more complex exceptions left. > > (Similar considerations would also apply to the Constraint node type.) In this updated patch set, I have also added the treatment of the Constraint type. (I also noted that the manual read/write functions for the Constraint type are out-of-sync again, so simplifying this would be really helpful.) I have also added commit messages to each patch. The way I have re-ordered the patch series now, I think patches 0001 through 0003 are candidates for inclusion after review, patch 0004 still needs a bit more analysis and testing, as described therein.
В списке pgsql-hackers по дате отправления