> > PostgreSQL seem to have a lot of names;
> >   Postgres 95, Postgres, Pg, Pgsql ... All these names are used in
> >   FAQ, filenames, docs, installation info, messages etc.
> >
> > Examples:
> >   The backend executable is 'postgres', why not 'postgresql'?
> >   INSTALL: "User postgres is the Postgres superuser"?
> >
> > I think it would be a good idea to use only "PostgreSQL" in all
> > docs, file names and so on, and "pgsql" as the official abbrev.
> >
> > This is one of the things new users notice and find strange.
> > I know, because I did, and people I know did it too.
> 
> Added to TODO list.

Frankly, the voluminous docs, many adapted from the originals, seem to
read better using "Postgres" rather than "PostgreSQL" or "Postgres95". I
changed 'em all after defining what each is in the introduction. Would
be a good bit of work to change them back, particularly since folks
aren't volunteering in droves for work on documentation...

                        - Tom

In response to

• Re: [HACKERS] Small changes for the "no excuses" release at 1998-03-16 02:31:32 from Bruce Momjian

Responses

• Re: [DOCS] Re: [HACKERS] Small changes for the "no excuses" release at 1998-03-16 12:20:03 from Mattias Kregert
• Re: [DOCS] Re: [HACKERS] Small changes for the "no excuses" release at 1998-03-18 07:37:44 from Peter T Mount

pgsql-hackers by date

Next:	From: t-ishii	Date: 1998-03-16 06:20:36
	Subject: Re: [HACKERS] varchar() vs char16 performance
Previous:	From: Thomas G. Lockhart	Date: 1998-03-16 05:59:53
	Subject: Re: [HACKERS] datetime default 'now' broken?