From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Adjust things so that the query_string of a cached plan and the |
Date: | 2009-01-07 22:56:50 |
Message-ID: | 6929.1231369010@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> The alternative I was envisioning was to have it look at the
>> ActivePortal's query string. However, if you prefer to define the
>> function as returning the current client query, it's fine as-is.
>> We should make sure the documentation explains it like that however.
> Now that you told me about ActivePortal I have used that and it seems to
> work fine. Patch attached and applied; documentation updated.
Well, hold on a minute. I said that was an alternative to look at,
not that it was necessarily better. Can you define in words of one
syllable which queries will be exposed this way? I don't believe
it's "all of them".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-01-07 23:33:05 | Re: Re: [COMMITTERS] pgsql: Adjust things so that the query_string of a cached plan and the |
Previous Message | Bruce Momjian | 2009-01-07 22:54:46 | pgsql: Add comment about why BETWEEN uses operator strings and not |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-01-07 23:12:58 | Re: Proposal: new border setting in psql |
Previous Message | Bruce Momjian | 2009-01-07 22:56:32 | Re: Significant oversight in that #include-removal script |