pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
New man pages
9+ messages / 5 participants
[nested] [flat]

* New man pages
@ 1999-08-05 14:53  Thomas Lockhart <lockhart@alumni.caltech.edu>
  0 siblings, 2 replies; 9+ messages in thread

From: Thomas Lockhart @ 1999-08-05 14:53 UTC (permalink / raw)
  To: Postgres Hackers List <hackers@postgresql.org>; Postgres Documentation List <docs@postgresql.org>

I've posted a tarball of new man pages at

  ftp://postgresql.org/pub/doc/man.tar.gz

I *think* these are ready for prime time, or close to it. They are
generated completely automatically from the sgml sources, using some
patched perl utilities. I'll try to post the complete set of docs
tools on the ftp site sometime soon.

Note that there are a few more man pages than were available in the
original versions, and that *all* information in the original man
pages appears in the new ones (or somewhere in the other docs).

I haven't yet updated the cvs tree to contain these new man pages.
Please look through the tarball and report any problems you see, if
you have any interest in the man page issue. Also, please report if
they look OK, so I know *someone* looked at them ;)

                   - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: [DOCS] New man pages
@ 1999-08-06 15:02  Bruce Momjian <maillist@candle.pha.pa.us>
  parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
  1 sibling, 1 reply; 9+ messages in thread

From: Bruce Momjian @ 1999-08-06 15:02 UTC (permalink / raw)
  To: Thomas Lockhart <lockhart@alumni.caltech.edu>; +Cc: Postgres Hackers List <hackers@postgreSQL.org>; Postgres Documentation List <docs@postgreSQL.org>

> I've posted a tarball of new man pages at
> 
>   ftp://postgresql.org/pub/doc/man.tar.gz
> 
> I *think* these are ready for prime time, or close to it. They are
> generated completely automatically from the sgml sources, using some
> patched perl utilities. I'll try to post the complete set of docs
> tools on the ftp site sometime soon.
> 
> Note that there are a few more man pages than were available in the
> original versions, and that *all* information in the original man
> pages appears in the new ones (or somewhere in the other docs).
> 
> I haven't yet updated the cvs tree to contain these new man pages.
> Please look through the tarball and report any problems you see, if
> you have any interest in the man page issue. Also, please report if
> they look OK, so I know *someone* looked at them ;)

I looked at the new pages, and they looked very good, much better than I
thought they would.  The only problem was the display of the command
syntax was wrapped rather than being one operator per line:

       select [distinct [on attr_name]]
           expression1 [as attr_name-1]
           {, expression-1 [as attr_name-i]}
           [into [temp] [table] classname]
           [from from-list]
           [where where-clause]
           [group by attr_name1 {, attr_name-i....}]
           [having having-clause]

became:

       select [distinct [on attr_name]]  expression1 [as attr_name-1]
           {, expression-1 [as attr_name-i]} [into [temp] [table] classname]
           [from from-list] [where where-clause] [group by attr_name1 
	   {, attr_name-i....}] [having having-clause]

Which is almost unreadable.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: [DOCS] New man pages
@ 1999-08-06 15:28  Thomas Lockhart <lockhart@alumni.caltech.edu>
  parent: Bruce Momjian <maillist@candle.pha.pa.us>
  0 siblings, 1 reply; 9+ messages in thread

From: Thomas Lockhart @ 1999-08-06 15:28 UTC (permalink / raw)
  To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: Postgres Hackers List <hackers@postgreSQL.org>; Postgres Documentation List <docs@postgreSQL.org>

> I looked at the new pages, and they looked very good, much better than I
> thought they would.

:)

>  The only problem was the display of the command
> syntax was wrapped rather than being one operator per line:
> Which is almost unreadable.

Fixed it.

                     - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: [DOCS] New man pages
@ 1999-08-06 15:52  Bruce Momjian <maillist@candle.pha.pa.us>
  parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
  0 siblings, 0 replies; 9+ messages in thread

From: Bruce Momjian @ 1999-08-06 15:52 UTC (permalink / raw)
  To: Thomas Lockhart <lockhart@alumni.caltech.edu>; +Cc: Postgres Hackers List <hackers@postgreSQL.org>; Postgres Documentation List <docs@postgreSQL.org>

> > I looked at the new pages, and they looked very good, much better than I
> > thought they would.
> 
> :)

Yes, I was prepared to really lose some of the nice formatting we had,
but we really didn't lose anything.

> 
> >  The only problem was the display of the command
> > syntax was wrapped rather than being one operator per line:
> > Which is almost unreadable.
> 
> Fixed it.

Thanks.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: [HACKERS] New man pages
@ 1999-08-09 13:26  José Soares <jose@sferacarta.com>
  parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
  1 sibling, 1 reply; 9+ messages in thread

From: José Soares @ 1999-08-09 13:26 UTC (permalink / raw)
  To: Thomas Lockhart <lockhart@alumni.caltech.edu>; +Cc: Postgres Hackers List <hackers@postgresql.org>

Hi Thomas,

I'm looking at man pages, and I find it very good. Now we have only one
documentation's version. Nice job.
There's only a little thing that I would like to recall your attention;
I see whenever the name Postgres instead of
PostgreSQL. Is there a reason to continue to call it Postgres in the
docs ?

-------------------------------------------------------------------------

UPDATE(l)                                               UPDATE(l)

NAME
       UPDATE - Replaces values of columns in a table

SYNOPSIS
       UPDATE  table  SET  R">colle> = expression [, ...]  [ FROM
                                          ^^^^^^^
       fromlist ] [ WHERE condition ]

   INPUTS
       table  The name of an existing table.

       column The name of a column in table.

       expression
              A valid expression or value to assign to column.

       fromlist
              A Postgres non-standard extension to allow  columns
                  ^^^^^^^
              from other tables to appear in the WHERE condition.

José


Thomas Lockhart ha scritto:

> I've posted a tarball of new man pages at
>
>   ftp://postgresql.org/pub/doc/man.tar.gz
>
> I *think* these are ready for prime time, or close to it. They are
> generated completely automatically from the sgml sources, using some
> patched perl utilities. I'll try to post the complete set of docs
> tools on the ftp site sometime soon.
>
> Note that there are a few more man pages than were available in the
> original versions, and that *all* information in the original man
> pages appears in the new ones (or somewhere in the other docs).
>
> I haven't yet updated the cvs tree to contain these new man pages.
> Please look through the tarball and report any problems you see, if
> you have any interest in the man page issue. Also, please report if
> they look OK, so I know *someone* looked at them ;)
>
>                    - Thomas
>
> --
> Thomas Lockhart                         lockhart@alumni.caltech.edu
> South Pasadena, California




^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: [HACKERS] New man pages
@ 1999-08-09 14:11  Thomas Lockhart <lockhart@alumni.caltech.edu>
  parent: José Soares <jose@sferacarta.com>
  0 siblings, 1 reply; 9+ messages in thread

From: Thomas Lockhart @ 1999-08-09 14:11 UTC (permalink / raw)
  To: José Soares <jose@sferacarta.com>; +Cc: Postgres Hackers List <hackers@postgresql.org>

> There's only a little thing that I would like to recall your attention;
> I see whenever the name Postgres instead of
> PostgreSQL. Is there a reason to continue to call it Postgres in the
> docs ?

I have chosen to use "Postgres" within the docs, as a shorter (and
pronouncable ;) form of our product. "PostgreSQL" appears in all
titles and introductory material. I have considered the "SQL" part of
the "PostgreSQL" as sort of a version or branch, like "OpenIngres" or
"Windows 2000", and a bit cumbersome in the body of the docs.

But that was a choice which can always be reconsidered, we're just a
"sed" away from a different name...

                      - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: [HACKERS] New man pages
@ 1999-08-09 14:45  Bruce Momjian <maillist@candle.pha.pa.us>
  parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
  0 siblings, 2 replies; 9+ messages in thread

From: Bruce Momjian @ 1999-08-09 14:45 UTC (permalink / raw)
  To: Thomas Lockhart <lockhart@alumni.caltech.edu>; +Cc: [Jos_] Soares <jose@sferacarta.com>; Postgres Hackers List <hackers@postgreSQL.org>

> > There's only a little thing that I would like to recall your attention;
> > I see whenever the name Postgres instead of
> > PostgreSQL. Is there a reason to continue to call it Postgres in the
> > docs ?
> 
> I have chosen to use "Postgres" within the docs, as a shorter (and
> pronouncable ;) form of our product. "PostgreSQL" appears in all
> titles and introductory material. I have considered the "SQL" part of
> the "PostgreSQL" as sort of a version or branch, like "OpenIngres" or
> "Windows 2000", and a bit cumbersome in the body of the docs.
> 
> But that was a choice which can always be reconsidered, we're just a
> "sed" away from a different name...

I vote for PostgreSQL.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: [HACKERS] New man pages
@ 1999-08-09 15:48  Thomas Good <tomg@nrnet.org>
  parent: Bruce Momjian <maillist@candle.pha.pa.us>
  1 sibling, 0 replies; 9+ messages in thread

From: Thomas Good @ 1999-08-09 15:48 UTC (permalink / raw)
  To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: Thomas Lockhart <lockhart@alumni.caltech.edu>; [Jos_] Soares <jose@sferacarta.com>; Postgres Hackers List <hackers@postgresql.org>

On Mon, 9 Aug 1999, Bruce Momjian wrote:

> > > There's only a little thing that I would like to recall your attention;
> > > I see whenever the name Postgres instead of
> > > PostgreSQL. Is there a reason to continue to call it Postgres in the
> > > docs ?
> > 
> > I have chosen to use "Postgres" within the docs, as a shorter (and
> > pronouncable ;) form of our product. "PostgreSQL" appears in all
> > titles and introductory material. I have considered the "SQL" part of
> > the "PostgreSQL" as sort of a version or branch, like "OpenIngres" or
> > "Windows 2000", and a bit cumbersome in the body of the docs.
> > 
> > But that was a choice which can always be reconsidered, we're just a
> > "sed" away from a different name...
> 
> I vote for PostgreSQL.

I'm just an end user who loves the product...with an opinion.  ;-)

Although I never used postgres (i.e., prior to the suffix being appended)
I always use `postgres' in conversation both as it is easily pronounced
and as there is a rather noteable history/lineage.  When communicating
with other postgres fans I say pee-gee...

When I refer specfically to the newer incarnation I say Postgres SQL
(post-gress see-qwell) rather than postgreS-Q-L...

I don't really mind if the man pages get edited as if I ever choose to
read them to my 4 year old son I will swap in the generic name, on the
fly.  But we are not up to that point yet - my son is still learning
about grep.  ;-)

I fully appreciate what the name is designed to convey but it does not
roll off the tongue...so I kinda like Thomas' decision to stick with
the more generic term - and the more poetic.

Cheers,
Tom

------- North Richmond Community Mental Health Center -------

Thomas Good                                   MIS Coordinator
Vital Signs:                  tomg@ { admin | q8 } .nrnet.org
                                          Phone: 718-354-5528  
                                          Fax:   718-354-5056  
                              
/* Member: Computer Professionals For Social Responsibility */ 




^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: [HACKERS] New man pages
@ 1999-08-16 02:55  The Hermit Hacker <scrappy@hub.org>
  parent: Bruce Momjian <maillist@candle.pha.pa.us>
  1 sibling, 0 replies; 9+ messages in thread

From: The Hermit Hacker @ 1999-08-16 02:55 UTC (permalink / raw)
  To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: Thomas Lockhart <lockhart@alumni.caltech.edu>; [Jos_] Soares <jose@sferacarta.com>; Postgres Hackers List <hackers@postgreSQL.org>

On Mon, 9 Aug 1999, Bruce Momjian wrote:

> > > There's only a little thing that I would like to recall your attention;
> > > I see whenever the name Postgres instead of
> > > PostgreSQL. Is there a reason to continue to call it Postgres in the
> > > docs ?
> > 
> > I have chosen to use "Postgres" within the docs, as a shorter (and
> > pronouncable ;) form of our product. "PostgreSQL" appears in all
> > titles and introductory material. I have considered the "SQL" part of
> > the "PostgreSQL" as sort of a version or branch, like "OpenIngres" or
> > "Windows 2000", and a bit cumbersome in the body of the docs.
> > 
> > But that was a choice which can always be reconsidered, we're just a
> > "sed" away from a different name...
> 
> I vote for PostgreSQL.

I second it...whenever ppl mention "postgres", i think back to our
ancestor and figure they are referring to that :(


Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 




^ permalink  raw  reply  [nested|flat] 9+ messages in thread


end of thread, other threads:[~1999-08-16 02:55 UTC | newest]

Thread overview: 9+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-08-05 14:53 New man pages Thomas Lockhart <lockhart@alumni.caltech.edu>
1999-08-06 15:02 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-08-06 15:28   ` Thomas Lockhart <lockhart@alumni.caltech.edu>
1999-08-06 15:52     ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-08-09 13:26 ` José Soares <jose@sferacarta.com>
1999-08-09 14:11   ` Thomas Lockhart <lockhart@alumni.caltech.edu>
1999-08-09 14:45     ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-08-09 15:48       ` Thomas Good <tomg@nrnet.org>
1999-08-16 02:55       ` The Hermit Hacker <scrappy@hub.org>

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