Add GUC_REPORT to server_encoding, integer_datetimes

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Add GUC_REPORT to server_encoding, integer_datetimes
Date: 2004-08-13 03:38:55
Message-ID: 411C37CF.7010000@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

This adds GUC_REPORT to server_encoding and integer_datetimes so they
are reported in the V3 protocol startup packet. Also some related doc
updates.

Rationale:

1) server_encoding is useful to allow clients to detect bad
server/client encoding pairs. The one that bites JDBC regularly is
client_encoding = UNICODE with server_encoding = SQL_ASCII. I'd prefer
for the server to reject that combination entirely, but failing that
clients can implement such a policy themselves by inspecting
server_encoding when establishing a connection.

2) integer_datetimes affects the binary representation of date/time
types. A client that wants to use binary parameters or resultsets that
involve those types needs to know the value of this setting before
dealing with the binary data.

In both cases, it's good to have it in the startup packet to avoid an
extra round-trip on connection establishment.

Any chance that this can go into 8.0?

-O

Attachment Content-Type Size
pgsql-server-guc-reports.txt text/plain 6.3 KB

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2004-08-13 03:53:54 Re: make fails if path has spaces
Previous Message Andrew Dunstan 2004-08-13 03:37:38 Re: [PATCHES] Patch for pg_dump: Multiple -t options and