1. 26 Jul, 1998 1 commit
    • Marc G. Fournier's avatar
      · 5979d738
      Marc G. Fournier authored
      From: t-ishii@sra.co.jp
      
      As Bruce mentioned, this is due to the conflict among changes we made.
      Included patches should fix the problem(I changed all MB to
      MULTIBYTE). Please let me know if you have further problem.
      
      P.S. I did not include pathces to configure and gram.c to save the
      file size(configure.in and gram.y modified).
      5979d738
  2. 24 Jul, 1998 1 commit
    • Marc G. Fournier's avatar
      · bf00bbb0
      Marc G. Fournier authored
      I really hope that I haven't missed anything in this one...
      
      From: t-ishii@sra.co.jp
      
      Attached are patches to enhance the multi-byte support.  (patches are
      against 7/18 snapshot)
      
      * determine encoding at initdb/createdb rather than compile time
      
      Now initdb/createdb has an option to specify the encoding. Also, I
      modified the syntax of CREATE DATABASE to accept encoding option. See
      README.mb for more details.
      
      For this purpose I have added new column "encoding" to pg_database.
      Also pg_attribute and pg_class are changed to catch up the
      modification to pg_database.  Actually I haved added pg_database_mb.h,
      pg_attribute_mb.h and pg_class_mb.h. These are used only when MB is
      enabled. The reason having separate files is I couldn't find a way to
      use ifdef or whatever in those files. I have to admit it looks
      ugly. No way.
      
      * support for PGCLIENTENCODING when issuing COPY command
      
      commands/copy.c modified.
      
      * support for SQL92 syntax "SET NAMES"
      
      See gram.y.
      
      * support for LATIN2-5
      * add UNICODE regression test case
      * new test suite for MB
      
      New directory test/mb added.
      
      * clean up source files
      
      Basic idea is to have MB's own subdirectory for easier maintenance.
      These are include/mb and backend/utils/mb.
      bf00bbb0
  3. 06 Apr, 1998 2 commits
    • Bruce Momjian's avatar
      Makefile cleanup./ · c61846e5
      Bruce Momjian authored
      c61846e5
    • Bruce Momjian's avatar
      Hi, · 1e801a8f
      Bruce Momjian authored
      Attached you'll find a (big) patch that fixes make dep and make
      depend in all Makefiles where I found it to be appropriate.
      
      It also removes the dependency in Makefile.global for NAMEDATALEN
      and OIDNAMELEN by making backend/catalog/genbki.sh and bin/initdb/initdb.sh
      a little smarter.
      
      This no longer requires initdb.sh that is turned into initdb with
      a sed script when installing Postgres, hence initdb.sh should be
      renamed to initdb (after the patch has been applied :-) )
      
      This patch is against the 6.3 sources, as it took a while to
      complete.
      
      Please review and apply,
      
      Cheers,
      
      Jeroen van Vianen
      1e801a8f
  4. 07 Nov, 1997 1 commit
  5. 30 Oct, 1997 1 commit
  6. 25 Aug, 1997 2 commits
  7. 26 Apr, 1997 1 commit
  8. 13 Nov, 1996 1 commit
  9. 11 Nov, 1996 1 commit
  10. 13 Aug, 1996 1 commit
    • Marc G. Fournier's avatar
      I have attached a minor update for the Postgres make files. This update · ca5db6ca
      Marc G. Fournier authored
      does 2 things:
      
      1) Make it hard to not notice the make failed.  (As you recall, someone on
         the mailing list had this problem.  I've had it to some extent myself).
      
          The 1.02 make files continue with the next subdirectory when a make
          in a subdirectory fails.  The patch makes the make stop in the
          conventional way when a submake fails.  It also adds a reassuring message
          when the make succeeds and adds a note to the INSTALL file to expect it.
      
      2) Include loader flags on all invocations of the linker.
      
         The 1.02 make files omit the $(LDFLAGS) on some of the linker invocations.
         On my system, I need one of those flags just to make it invoke the proper
         version of the compiler/linker, so LDFLAGS has to be everywhere.
      
      Submitted by: Bryan Henderson <bryanh@giraffe.netgate.net>
      ca5db6ca
  11. 25 Jul, 1996 1 commit
  12. 23 Jul, 1996 1 commit
  13. 09 Jul, 1996 1 commit