> On Sun, 19 Aug 2001, Tom Lane wrote:
> > One thing that I find absolutely essential for dealing with any large
> > project is a full-text indexer (I use Glimpse, but I think there are
> > others out there). Being able to quickly look at every use of a
> > particular identifier goes a long way t
> Hi all,
>
> For a few months now I've been thinking about whether or not a guide
> ('line-by-line') to the Postgres source tree would be of any value.
>
> Such a guide would, most probably, trace an 'ultimate' query (ie,
> one which requires the use of all source level functionality) through
On Sun, 19 Aug 2001, Tom Lane wrote:
> One thing that I find absolutely essential for dealing with any large
> project is a full-text indexer (I use Glimpse, but I think there are
> others out there). Being able to quickly look at every use of a
> particular identifier goes a long way towards ans
"Serguei Mokhov" <[EMAIL PROTECTED]> writes:
> And what's wrong in automated guide generation?
Even more to the point, what's wrong with looking at the source code?
(Why would you want a "line by line" guide if you're not looking at the
source code, anyway?)
We could probably do with more extens
- Original Message -
From: Gavin Sherry <[EMAIL PROTECTED]>
Sent: Sunday, August 19, 2001 3:40 AM
> Hi all,
>
> For a few months now I've been thinking about whether or not a guide
> ('line-by-line') to the Postgres source tree would be of any value.
[snip]
> So, what do people th
