Skip to content

Fix incorrect ParameterStatus key casing for DateStyle, TimeZone, and IntervalStyle#5146

Merged
renecannao merged 2 commits intov3.0from
v3.0_parameter_status_case_sensitive_issue_5145
Oct 14, 2025
Merged

Fix incorrect ParameterStatus key casing for DateStyle, TimeZone, and IntervalStyle#5146
renecannao merged 2 commits intov3.0from
v3.0_parameter_status_case_sensitive_issue_5145

Conversation

@rahim-kanji
Copy link
Collaborator

Summary

PostgreSQL clients treat ParameterStatus message names as case-sensitive and expect canonical capitalization for certain parameters.
Three parameters in PostgreSQL use capitalized names instead of lowercase for historical reasons:

  • DateStyle
  • TimeZone
  • IntervalStyle

These parameters predate the unified GUC (Grand Unified Configuration) system and retained their mixed-case names for backward compatibility.
Because ProxySQL previously sent them as datestyle, timezone, and intervalstyle, some PostgreSQL clients failed to recognize them and ignored their values.

Fix

  • Updated ProxySQL to send canonical capitalization for DateStyle, TimeZone, and IntervalStyle.
  • All other ParameterStatus keys continue to use lowercase names, consistent with PostgreSQL.

Closes #5145

…valStyle

These parameters use capitalized names in PostgreSQL for historical reasons.
ProxySQL now sends them using canonical capitalization to ensure client compatibility.
@gemini-code-assist
Copy link

Summary of Changes

Hello @rahim-kanji, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical compatibility issue with PostgreSQL clients that are sensitive to the casing of ParameterStatus message names. It specifically targets DateStyle, TimeZone, and IntervalStyle, which require canonical capitalization. By adjusting how ProxySQL sends these parameter names and refining the internal handling of variable names, the change ensures proper recognition and application of these settings by PostgreSQL clients, thereby enhancing overall system interoperability and preventing configuration discrepancies.

Highlights

  • ParameterStatus Key Casing: Corrected the casing for specific PostgreSQL ParameterStatus message names (DateStyle, TimeZone, and IntervalStyle) from lowercase to their canonical capitalized form, as required by PostgreSQL clients.
  • Client Compatibility: Resolved an issue where PostgreSQL clients failed to recognize and apply values for these parameters due to incorrect casing, improving interoperability.
  • Internal Variable Handling: Adjusted internal logic to correctly differentiate between set_variable_name (for client-facing ParameterStatus messages) and internal_variable_name (for internal lookups and JSON session data), ensuring the appropriate casing is used in each context.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly addresses an issue with the case-sensitivity of certain PostgreSQL ParameterStatus message names by updating DateStyle, TimeZone, and IntervalStyle to use their canonical capitalized forms. The changes are logical and well-implemented, ensuring that client-facing communication uses the correct capitalization while internal matching remains case-insensitive. The related adjustments in other files improve code robustness. I have one suggestion to enhance the variable matching logic for better correctness and clarity.

@rahim-kanji rahim-kanji force-pushed the v3.0_parameter_status_case_sensitive_issue_5145 branch from 83596fa to dc6db35 Compare October 5, 2025 20:50
@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 5, 2025

@renecannao renecannao merged commit 413b012 into v3.0 Oct 14, 2025
145 of 154 checks passed
@renecannao renecannao deleted the v3.0_parameter_status_case_sensitive_issue_5145 branch March 7, 2026 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix incorrect ParameterStatus key casing for DateStyle, TimeZone, and IntervalStyle

2 participants