Thread: Re: The name of the game (was Re: postgre linkage with non-postgre

Tom Lane wrote:
> Arguably,
> the 1996 decision to call it PostgreSQL instead of reverting to
> plain Postgres was the single worst mistake this project ever made.
> It seems far too late to change now, though.

How can it be too late?  If Borland/Inprise/Borland can do it
and if AT&T/SBC/AT&T can do it, couldn't this project do it too?

I think most of us are all too familiar wasting time explaining
"Postgre S.Q.L." that most newbies assume.  And it's hard to blame
them.  Ask any kid learning to read how PostgreSQL is pronounced and
they won't group the "S" with the "gre" either.  If we really want
people to pronounce it "post-gres-cue-ell" at least change the
capitalization to "PostgresQL".

But surely it'd be a better idea for everyone if for 8.2 or 9.0
or whatever if the project formally made Postgres not only an
acceptable but a preferred name for the project, wouldn't it?

Still watching advocacy list and want to tell you that I very much
appreciate this discussion.

Ron Mayer wrote:
> How can it be too late?  If Borland/Inprise/Borland can do it
> and if AT&T/SBC/AT&T can do it, couldn't this project do it too?
Yes. In way of reverting back to an earlier name makes me by far less
headache like changing to a completely different new name.
This is especially because many people - at least here in Germany -
still use "Postgres" because they don't want to discrace themselves by
pronouncing PostgreSQL wrongly. I like the message the 'SQL' carries,
however most people, that know what SQL is and respect it, do know about
the strong SQL compliance of PostgreSQL.

Last not least, it would be like taking a bow toward the history of this
great project.
>
> But surely it'd be a better idea for everyone if for 8.2 or 9.0
> or whatever if the project formally made Postgres not only an
> acceptable but a preferred name for the project, wouldn't it?
I appreciate your suggestion. Even if we would not do a big hoopla on
the name reverting.


Well, due to some expierence with changing name of software: Will there
be any implication in source-code, installation procedures or running
production systems?


Anastasios