Re: cutting down the TODO list thread - Mailing list pgsql-hackers
| From | John Naylor |
|---|---|
| Subject | Re: cutting down the TODO list thread |
| Date | |
| Msg-id | CAFBsxsF-uA=SvFNJGNin68KRfrCautEwEN0JL4EimGaUM0zcsg@mail.gmail.com Whole thread Raw |
| In response to | Re: cutting down the TODO list thread (John Naylor <john.naylor@enterprisedb.com>) |
| Responses |
Re: cutting down the TODO list thread
(Bruce Momjian <bruce@momjian.us>)
Re: cutting down the TODO list thread (Tom Lane <tgl@sss.pgh.pa.us>) |
| List | pgsql-hackers |
Here are the next couple of sections with items proposed to be moved to the "not worth doing" page. As before, if there are any objections, let me know. I'll make the move in a few days.
Also, since 13 has been released, I'll change the explanation of Done items to "will appear in the PostgreSQL 14 release." Also, since that wasn't updated, it's not immediately clear to me which release the [D] marking for "improve setting of visibility map bits for read-only and insert-only workloads" refers to. Does anyone know which commit that is?
*Functions
- Enforce typmod for function inputs, function results and parameters for spi_prepare'd statements called from PLs
Lack of consensus
- Reduce memory usage of aggregates in set returning functions
The issue and proposed patch is likely no longer an important thing to improve in this area nowadays.
- Fix /contrib/ltree operator
Bug from 2007 with zero followup
- Fix /contrib/btree_gist's implementation of inet indexing
Bug from 2010 and apparent lack of interest
*Character Formatting (this entire section would be removed)
- Allow to_date() and to_timestamp() to accept localized month names
The following attempts to pick this from the TODO list in 2008 didn't go anywhere:
https://www.postgresql.org/message-id/flat/010401c86788%246f1ddb60%240a01a8c0%40gevmus
https://www.postgresql.org/message-id/flat/CA%2BheTbrDQ6b0Am_mk0dJEcwNxwQz%2Br%3Daz_%3DzHTva%2B5BDnfOKjA%40mail.gmail.com
- Add missing parameter handling in to_char()
Very old
- Throw an error from to_char() instead of printing a string of "#" when a number doesn't fit in the desired output format.
Lack of consensus
- Fix to_number() handling for values not matching the format string
Large amount of work for questionable benefit
*Multi-Language Support
- Add a cares-about-collation column to pg_proc, so that unresolved-collation errors can be thrown at parse time
Proposed while listing open items during 9.1. Doesn't seem to justify the amount of work it would take.
- Add octet_length_server() and octet_length_client()
- Make octet_length_client() the same as octet_length()?
Very old
- Improve UTF8 combined character handling?
Too vague
- Fix problems with wrong runtime encoding conversion for NLS message files
What problems? There is no discussion thread.
- More sensible support for Unicode combining characters, normal forms
We have normalization as of PG13, so I propose to mark this Done rather than move it.
--
John Naylor
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
- Enforce typmod for function inputs, function results and parameters for spi_prepare'd statements called from PLs
Lack of consensus
- Reduce memory usage of aggregates in set returning functions
The issue and proposed patch is likely no longer an important thing to improve in this area nowadays.
- Fix /contrib/ltree operator
Bug from 2007 with zero followup
- Fix /contrib/btree_gist's implementation of inet indexing
Bug from 2010 and apparent lack of interest
*Character Formatting (this entire section would be removed)
- Allow to_date() and to_timestamp() to accept localized month names
The following attempts to pick this from the TODO list in 2008 didn't go anywhere:
https://www.postgresql.org/message-id/flat/010401c86788%246f1ddb60%240a01a8c0%40gevmus
https://www.postgresql.org/message-id/flat/CA%2BheTbrDQ6b0Am_mk0dJEcwNxwQz%2Br%3Daz_%3DzHTva%2B5BDnfOKjA%40mail.gmail.com
- Add missing parameter handling in to_char()
Very old
- Throw an error from to_char() instead of printing a string of "#" when a number doesn't fit in the desired output format.
Lack of consensus
- Fix to_number() handling for values not matching the format string
Large amount of work for questionable benefit
*Multi-Language Support
- Add a cares-about-collation column to pg_proc, so that unresolved-collation errors can be thrown at parse time
Proposed while listing open items during 9.1. Doesn't seem to justify the amount of work it would take.
- Add octet_length_server() and octet_length_client()
- Make octet_length_client() the same as octet_length()?
Very old
- Improve UTF8 combined character handling?
Too vague
- Fix problems with wrong runtime encoding conversion for NLS message files
What problems? There is no discussion thread.
- More sensible support for Unicode combining characters, normal forms
We have normalization as of PG13, so I propose to mark this Done rather than move it.
--
John Naylor
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
pgsql-hackers by date: