Dear Hackers, I perfectly missed mails and 8/9 was a national holiday. I must apologize about anything. Very sorry for inconvenience.
> The RMT's first responsibility is to ensure that PostgreSQL 14 is > released on schedule. We would prefer to avoid a revert, but we cannot > allow this to drag on indefinitely. Of cause I will try to avoid it but I can understand doing your business. Dear Meskes, I summarize the thread. As you might know DECLARE STATEMENT has been added from PG14, but I found that connection-control feature cannot be used for DEALLOCATE and DESCRIBE statement (More details, please see patches or ask me). But we have a question - what statement should use the associated connection? Obviously DEALLOCATE statement should follow the linked connection because the statement uses only one sql identifier. In DESCRIBE or any other descriptor-related statements, however, I think it is non-obvious because they have also descriptor-name. Currently I made patches that includes about DESCRIBE, but I'm wondering this approach is correct. I want you to ask your opinion about the scope of DECLARE STATEMENT. Coding is not hard hence I think we can fix this until the end of Sep. if we set a policy correctly and have reviewers. Best Regards, Hayato Kuroda FUJITSU LIMITED
