Re: Naming conventions

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Raymond O'Donnell <rod(at)iol(dot)ie>
Cc: Scott Briggs <scott(dot)br(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Naming conventions
Date: 2012-09-02 12:42:24
Message-ID: 20120902124224.GB24137@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, May 25, 2012 at 09:49:18AM +0100, Raymond O'Donnell wrote:
> On 25/05/2012 02:21, Bruce Momjian wrote:
> > On Wed, May 16, 2012 at 10:08:03AM +0100, Raymond O'Donnell wrote:
> >> On 15/05/2012 22:50, Scott Briggs wrote:
> >>> So this is purely anecdotal but I'm curious, what's with all the
> >>> different naming conventions? There's psql (for database
> >>> connections), pgsql (used for some dirs like /usr/pgsql-9.1 and this
> >>> mailing list), postgres (user and other references), and postgresql
> >>> (startup scripts).
> >
> > Uh, the original Berkeley project name was postgres, pgsql is used as a
> > short-hand for PostgreSQL, and psql is short for 'PostgreSQL SQL
> > Monitor'.
> >
> >> ... and don't forget (maybe oddest of all) libpq! :-)
> >
> > libpq originally supported Postgres QUEL:
> >
> > http://en.wikipedia.org/wiki/QUEL_query_languages
> >
>
> Good to know all this... it might be worth adding it to the website or
> the wiki for the benefit of us blow-ins. :-)

Added a small mention to our docs in the history section that libpq is
named after POSTQUEL. Applied patch attached.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

Attachment Content-Type Size
quel.diff text/x-diff 1008 bytes

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2012-09-02 13:16:51 Re: Dtrace for tracing PostgreSQL link not working
Previous Message Bruce Momjian 2012-09-02 12:12:33 Re: [GENERAL] Multiple Slave Failover with PITR