| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [v9.2] Add GUC sepgsql.client_label |
| Date: | 2012-02-11 18:36:21 |
| Message-ID: | 4F3660C502000025000453AD@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" wrote:
Tom Lane wrote:
>> I agree it's a bug that you can do what Kevin's example shows.
>
> I'll look at it and see if I can pull together a patch.
Attached.
Basically, if a GUC has a check function, this patch causes it to be
run on a RESET just like it is on a SET, to make sure that the
resulting value is valid to set within the context. Some messages
needed adjustment. While I was there, I made cod a little more
consistent among related GUCs.
I also added a little to the regression tests to cover this.
-Kevin
| Attachment | Content-Type | Size |
|---|---|---|
| check-reset-v1.patch | application/octet-stream | 9.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2012-02-11 19:34:31 | Re: Memory usage during sorting |
| Previous Message | Andrew Dunstan | 2012-02-11 18:18:59 | Re: auto_explain produces invalid JSON |