| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Checks for command string |
| Date: | 2006-01-02 01:15:52 |
| Message-ID: | 26588.1136164552@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Barring making a fourth GUC variable to control them (which seems like
>> overkill), I think it's a reasonably sane definition to say "we count
>> these if any stats are being collected". Doing what you propose would
>> simply expose an irrelevant implementation detail to users.
> OK. Don't we need to document this somewhere?
No objection to that. Probably section 24.2.1 is a reasonable place?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-02 01:17:15 | Re: Checks for command string |
| Previous Message | Bruce Momjian | 2006-01-02 01:14:44 | Re: EINTR error in SunOS |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-02 01:17:15 | Re: Checks for command string |
| Previous Message | Bruce Momjian | 2006-01-02 01:11:27 | Re: Checks for command string |