Problem with new Collate change

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>
Subject: Problem with new Collate change
Date: 2001-12-10 10:01:08
Message-ID: 200112101001.fBAA18T00283@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs


Can I ask why a full path of /usr/bin/ was added to collateindex.pl with
no discussion and no mention in the cvs logs? This broke my automatic
build because my binary is in the sgml binary directory. Can it be put
back?

Thanks.

> CVSROOT: /cvsroot
> Module name: pgsql
> Changes by: thomas(at)postgresql(dot)org 01/12/07 22:24:40
>
> Modified files:
> doc/src/sgml : Makefile cvs.sgml datatype.sgml docguide.sgml
> installation.sgml syntax.sgml
>
> Log message:
> Update list of currently supported platforms.
> Mention SQL9x precision syntax for date/time types.
> Use PostgreSQL consistantly throughout docs. Before, usage was split evenly
> between Postgres and PostgreSQL.
>
> Modified files:
> doc/src/sgml/ref: abort.sgml allfiles.sgml alter_group.sgml
> alter_table.sgml alter_user.sgml analyze.sgml
> begin.sgml close.sgml cluster.sgml
> comment.sgml commit.sgml copy.sgml
> create_aggregate.sgml create_constraint.sgml
> create_database.sgml create_function.sgml
> create_group.sgml create_index.sgml
> create_language.sgml create_operator.sgml
> create_rule.sgml create_sequence.sgml
> create_table.sgml create_table_as.sgml
> create_trigger.sgml create_type.sgml
> create_user.sgml create_view.sgml
> createdb.sgml createlang.sgml createuser.sgml
> current_time.sgml current_timestamp.sgml
> current_user.sgml declare.sgml delete.sgml
> drop_aggregate.sgml drop_database.sgml
> drop_function.sgml drop_group.sgml
> drop_index.sgml drop_language.sgml
> drop_operator.sgml drop_rule.sgml
> drop_sequence.sgml drop_table.sgml
> drop_trigger.sgml drop_type.sgml
> drop_user.sgml drop_view.sgml dropdb.sgml
> droplang.sgml dropuser.sgml ecpg-ref.sgml
> end.sgml explain.sgml fetch.sgml grant.sgml
> initdb.sgml initlocation.sgml insert.sgml
> ipcclean.sgml listen.sgml lock.sgml move.sgml
> notify.sgml pg_ctl-ref.sgml pg_dump.sgml
> pg_dumpall.sgml pg_passwd.sgml pg_upgrade.sgml
> pgaccess-ref.sgml pgtclsh.sgml pgtksh.sgml
> postgres-ref.sgml postmaster.sgml
> psql-ref.sgml reindex.sgml reset.sgml
> revoke.sgml rollback.sgml select.sgml
> select_into.sgml set.sgml set_transaction.sgml
> show.sgml truncate.sgml unlisten.sgml
> update.sgml vacuum.sgml vacuumdb.sgml
>
> Log message:
> Use PostgreSQL consistantly throughout docs. Before, usage was split evenly
> between Postgres and PostgreSQL.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>

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

Browse pgsql-docs by date

  From Date Subject
Next Message Justin Clift 2001-12-17 07:25:21 Need to include the length of trigger names
Previous Message Bruce Momjian 2001-12-05 23:09:26 Re: <application> vs <command>