Re: Using Postgres as an alias - Mailing list pgsql-advocacy
From | Pavel Stehule |
---|---|
Subject | Re: Using Postgres as an alias |
Date | |
Msg-id | 162867790709261503o70182b43s669422b1ed21fc43@mail.gmail.com Whole thread Raw |
In response to | Re: Using Postgres as an alias (Bruce Momjian <bruce@momjian.us>) |
Responses |
Re: Using Postgres as an alias
Re: Using Postgres as an alias Re: Using Postgres as an alias |
List | pgsql-advocacy |
Hello Bruce I really unlike this game about change the name. If you get 100% support then situation is simple, but you hasn't it. I use PostgreSQL, Postgres and I doesn't any strong benefit with change of name. Devrim's argument about renaming all packages is really strong for me. I agree so official documentation have to use only name PostgreSQL. Is technical documentation not articles. And again I don't see any benefit. Currently Postgres is well know synonym for PostgreSQL and there isn't necessary push it into documentation. Please stop it. Regards Pavel Stehule 2007/9/26, Bruce Momjian <bruce@momjian.us>: > Joshua D. Drake wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Bruce Momjian wrote: > > > Joshua D. Drake wrote: > > >> Bruce Momjian wrote: > > >>> Peter Eisentraut wrote: > > >>>> Bruce Momjian wrote: > > >>>>> But without such changes the alias is only in the FAQ and will not be > > >>>>> widely used. > > >>>> I'm not sure if this has been thought through to the end. If we make > > >>>> the point that PostgreSQL can also be called Postgres, this does not > > >>>> prevent anyone from calling it Postgre or any other forms that we might > > >>>> not like. It might in fact make people think that it has various names > > >>>> and you can call it whatever you want. > > >>> Well, they are already calling it "Postgre" without our help, so I see > > >>> us giving them a clear alternative to PostgreSQL as helping avoid > > >>> "Postgre". > > >>> > > >>> But in the end, they can continue calling us whatever they want and we > > >>> can't stop them. > > >> Then why are we bothering trying? > > > > > > Because though we can't _stop_ them, we can certainly influence them. > > > Why are you asking such simplistic questions? > > > > It seemed odd to me. You said, "we can't stop them". So it seems like an > > awful lot of wasted effort to try. > > Not sure why you see this as fatalist. I can't _make_ many people do > much, but I can encourage them to do things, as you have seen. That's > what we are doing here to encourage the use of "Postgres". > > -- > Bruce Momjian <bruce@momjian.us> http://momjian.us > EnterpriseDB http://postgres.enterprisedb.com > > + If your life is a hard drive, Christ can be your backup. + > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match >
pgsql-advocacy by date: