| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Dimitri Fontaine" <dimitri(at)2ndQuadrant(dot)fr>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com>, "Joe Conway" <mail(at)joeconway(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org, "Josh" <josh(at)schemaverse(dot)com> |
| Subject: | Re: SET variable - Permission issues |
| Date: | 2011-10-11 20:39:03 |
| Message-ID: | 3428.1318365543@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> wrote:
>> Adding the information visible at the right places is a fun
>> project in itself, too :)
> I was thinking a couple new columns in pg_settings (and what backs
> it) would be the main thing, but I haven't searched the source code
> yet. Does something else leap to mind for you?
This isn't exactly a trivial matter. What happens for instance if you
try to change the limit, and there are already active values outside the
limit in some processes?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2011-10-11 20:39:26 | Re: Overhead cost of Serializable Snapshot Isolation |
| Previous Message | Kevin Grittner | 2011-10-11 20:37:38 | Re: Overhead cost of Serializable Snapshot Isolation |