| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | Tomas Vondra <tv(at)fuzzy(dot)cz> | 
| Cc: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Re: WIP: explain analyze with 'rows' but not timing | 
| Date: | 2011-12-23 15:14:41 | 
| Message-ID: | 19043.1324653281@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Tomas Vondra <tv(at)fuzzy(dot)cz> writes:
> One thing I'm wondering about is that the InstrumentOptions are not
> exclusive - INSTRUMENT_TIMER means 'collect timing and row counts' while
> INSTRUMENT_ROWS means 'collect row counts'. Wouldn't it be better to
> redefine the INSTRUMENT_TIMER so that it collects just timing info. I.e.
> to get the current behaviour, you'd have to do this
> instrument_options |= (INSTRUMENT_TIMER | INSTRUMENT_ROWS)
> It's quite trivial change in explain.c, the problem I have with that is
> that it might break extensions.
I'm not especially concerned by that angle --- we make bigger API
changes all the time.  But you could change the name, eg
instrument_options |= (INSTRUMENT_TIMING | INSTRUMENT_ROWS)
and then #define INSTRUMENT_TIMER as the OR of the two real bits
for backward compatibility.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-12-23 15:18:21 | Re: xlog location arithmetic | 
| Previous Message | Andrew Dunstan | 2011-12-23 15:13:42 | Re: xlog location arithmetic |