From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] SGML index build fix |
Date: | 2007-01-07 05:42:06 |
Message-ID: | 200701070542.l075g6p24768@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Joshua D. Drake wrote:
> On Sat, 2007-01-06 at 23:38 -0500, Tom Lane wrote:
> > Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > > The attached patch warns users when they create documentation output
> > > that has no index, and suggests re-running 'gmake'.
> >
> > This is just useless noise. If it could tell the difference between an
> > up-to-date index and a not-up-to-date one, there might be some value
> > to it ... but as-is I think it's just getting in the user's face.
> > Everyone using these tools knows about the two-pass behavior.
>
> No, not everyone knows. In fact I would argue that most do not know. It
> isn't intuitive to the process. You *expect* that an index will be made.
The idea for the warning message actually came from Peter.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-01-07 08:25:49 | Re: Mark/Restore and avoiding RandomAccess sorts |
Previous Message | Joshua D. Drake | 2007-01-07 04:58:26 | Re: [HACKERS] SGML index build fix |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-01-07 08:28:17 | Re: COPY with no WAL, in certain circumstances |
Previous Message | Joshua D. Drake | 2007-01-07 04:58:26 | Re: [HACKERS] SGML index build fix |