Proposal to add GUC_REPORT to lc_monetary, lc_numeric and search_path - Mailing list pgsql-hackers

From Dave Cramer
Subject Proposal to add GUC_REPORT to lc_monetary, lc_numeric and search_path
Date
Msg-id CADK3HHK6RimOQYPDgFWPYWiD5TH_XECgV=yJOv+h9kfzT55P7A@mail.gmail.com
Whole thread Raw
Responses Re: Proposal to add GUC_REPORT to lc_monetary, lc_numeric and search_path  (Shay Rojansky <roji@roji.org>)
List pgsql-hackers
Hello,

The first 2 lc_monetary and lc_numeric are useful if the client for some reason executes set lc_*. We don't get a report and in many cases can't continue to parse numerics or money.
Now it it possible to get these at startup by issuing show or querying the catalog, but it seems much cleaner to just send them.

The latter is important for similar reasons. JDBC caches prepared statements internally and if the user changes the search path without using setSchema or uses a function to change it then internally it would be necessary to invalidate the cache. Currently if this occurs these statements fail.

This seems like a rather innocuous change as the protocol is not changed, rather the amount of information returned on startup is increased marginally.

I've included the authors of the npgsql and the node drivers in the email for their input.

Dave Cramer

pgsql-hackers by date:

Previous
From: Dent John
Date:
Subject: Re: [PATCH] get rid of StdRdOptions, use individual binary reloptionsrepresentation for each relation kind instead
Next
From: Jose Luis Tallon
Date:
Subject: Re: [PATCH] Implement uuid_version()