Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: explain analyze timings
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Magnus Hagander" <mha(at)sollentuna(dot)net>
- Cc: pgsql-hackers-win32(at)postgresql(dot)org, "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org>
- Subject: Re: explain analyze timings
- Date: Sun, 20 Mar 2005 12:42:58 -0500
- Message-id: <8032(dot)1111340578(at)sss(dot)pgh(dot)pa(dot)us>
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes: > Here's a patch that does just this. This seems about the ugliest and most intrusive way you could have done it :-(. A judicious typedef and macro or two could eliminate most of the #ifdefs and code duplication, thereby preserving readability... regards, tom lane
- References:
- Re: explain analyze timings
- From: Magnus Hagander
- Re: explain analyze timings
- Prev by Date: Re: Half filled xlogs
- Next by Date: Re: [HACKERS] snprintf causes regression tests
- Previous by thread: Re: explain analyze timings
- Next by thread: Re: explain analyze timings
- Indexes: