public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Josh Kupershmidt <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd
Date: Tue, 26 Apr 2011 12:43:06 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Excerpts from Bruce Momjian's message of mar abr 26 12:15:50 -0300 2011:
> Tom Lane wrote:
> > Peter Eisentraut <[email protected]> writes:
> > > On lr, 2011-03-12 at 09:13 -0500, Bruce Momjian wrote:
> > >> OK, it is not something worthwhile, or just something you don't have
> > >> time for.  If the later, can you give us a hint on how to fix it?
> > 
> > > I'm not even sure what the actual action item is supposed to be.
> > 
> > The last suggestion in the thread was to move the contrib docs up one
> > level in the hierarchy, ie each contrib module would get a chapter not a
> > sect1.
> 
> I think we would have to move "Additional Supplied Modules" up into its
> own book, and then list each module.  The problem is that there are 42
> modules so that list is going to be pretty long in the table of
> contents.

Also, most of the sections are pretty short.  Making each of them a
chapter seems a waste.  I think some of them deserve a full chapter
(dblink, citext?, hstore, intarray, ltree, pgbench, pgcrypto, pgtrgm?,
pg_upgrade, tablefunc), but most don't.  (Some of the others could,
perhaps, get moved under "Reference").

Would it work to move only some?

-- 
Álvaro Herrera <[email protected]>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

view thread (26+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox