proxysql

Commit Graph

Author	SHA1	Message	Date
Rene Cannao	de9da7dede	PostgreSQL: Fix connection_parameters_test for hostname resolution - Replace inet_addr() with getaddrinfo() in connect_server() to support hostname resolution (required for Docker DNS like "proxysql") - Add verbose header explaining test purpose and scenarios - Add connection info output showing host/port configuration - Add diagnostic output in connect_server for debugging	1 month ago
Rahim Kanji	dd589508f4	Added regression test	12 months ago
Rahim Kanji	4c918490a4	Added TAP test Note: - Using libpq to test ProxySQL's handling of undocumented parameters isn't possible, as libpq enforces a strict subset of PostgreSQL connection parameters as per the official documentation, rejecting any undocumented parameters. However, actual PostgreSQL servers accept additional parameters (e.g., extra_float_digits) and apply them at the connection/session level. To test this behavior, a raw socket is used to connect to a ProxySQL server and send custom built messages to communicate with ProxySQL. It currently works with plain text password authentication, without ssl support. - Failure due to an invalid parameter returned by the PostgreSQL server, differs from ProxySQL's behavior. PostgreSQL returns an error during the connection handshake phase, whereas in ProxySQL, the connection succeeds, but the error is encountered when executing a query. This is behaviour is intentional, as newer PostgreSQL versions may introduce new parameters that ProxySQL is not yet aware of.	1 year ago

Author

SHA1

Message

Date

Rene Cannao

de9da7dede

PostgreSQL: Fix connection_parameters_test for hostname resolution

- Replace inet_addr() with getaddrinfo() in connect_server() to support
  hostname resolution (required for Docker DNS like "proxysql")
- Add verbose header explaining test purpose and scenarios
- Add connection info output showing host/port configuration
- Add diagnostic output in connect_server for debugging

Rahim Kanji

dd589508f4

Added regression test

Rahim Kanji

4c918490a4

Added TAP test

Note:
  - Using libpq to test ProxySQL's handling of undocumented parameters isn't possible, as libpq enforces a strict subset of PostgreSQL
    connection parameters as per the official documentation, rejecting any undocumented parameters. However, actual
    PostgreSQL servers accept additional parameters (e.g., extra_float_digits) and apply them at the connection/session level.
    To test this behavior, a raw socket is used to connect to a ProxySQL server and send custom built messages to communicate
    with ProxySQL. It currently works with plain text password authentication, without ssl support.

  - Failure due to an invalid parameter returned by the PostgreSQL server, differs from ProxySQL's behavior.
    PostgreSQL returns an error during the connection handshake phase, whereas in ProxySQL, the connection succeeds,
    but the error is encountered when executing a query.
    This is behaviour is intentional, as newer PostgreSQL versions may introduce new parameters that ProxySQL is not yet aware of.

3 Commits (6d6015a2034dbee2ea4eb50d2e84381df008fa46)