1. 10 3月, 2000 2 次提交
  2. 09 3月, 2000 9 次提交
  3. 08 3月, 2000 10 次提交
    • B
      I've made a diff against the 7.0beta1 tree that accomplishes several things: · f43ec05d
      Bruce Momjian 提交于
              1) adds NetBSD shared lib support on both ELF and a.out platforms
      
              2) replaces "-L$(LIBPQDIR) -lpq" with "$(LIBPQ)" defined in
                 Makefile.global.  This makes it much easier to build stuff in
                 the source tree after you've already installed the libraries.
      
              3) adds TEMPLATEDIR in Makefile.global that indicates where the
                 database templates are stored.  This separates the template files
                 from real libraries that are installed in $(LIBDIR).
              4) changes include order of <readline/readline.h> and <readline.h>.
                 The latest GNU readline installs its headers under a readline
                 subdirectory.
      
      In addition to applying the patch below the following files need to be copied:
      
              backend/port/dynloader:
                      bsd.h -> netbsd.h
                      bsd.c -> netbsd.c
              include/port:
                      bsd.h -> netbsd.h
              makefiles:
                      Makefile.bsd -> Makefile.netbsd
      
      It would be great to see this incorporated into the source tree before
      the 7.0 release is cut.
      
              Thanks!
      
           -- Johnny C. Lam <lamj@stat.cmu.edu>
      f43ec05d
    • B
      Bruce and all: · 26c953e3
      Bruce Momjian 提交于
      Here's a patch to fix the " '.' not allowed in db path" problem I ran into.
      I removed '.' from the set of illegial characters, but added backtick. I also
      included an explicit test for attempting include a reference to a parent dir.
      
      How that?
      
      Ross
      26c953e3
    • B
      Reversed out inet patch. · ab7fd118
      Bruce Momjian 提交于
      ab7fd118
    • B
      Hi Peter, · 326e2155
      Bruce Momjian 提交于
       I try change prompt in the psql, but it is set '.' (as '%m') for
      non-TCP/IP
      connection. This small patch try use uname() information for non-TCP/IP
      instead '.'.
      
                                              Karel
      326e2155
    • B
      Hi, · eae5184d
      Bruce Momjian 提交于
       the to_char() source code is large, here are regression tests for
      numeric/timestamp/int8 part. It is probably enough test for formatting
      code in the formatting.c module. The others (float4/float8/int4) types
      share this formatting code and eventual bugs for these types aren't
      few probable.
      
       Patch fix timestamp_to_char() for infinity/invalid timestamp too.
      
      
                                                      Karel
      eae5184d
    • B
      Protects you from coredumps if you do eg. str::int4 where str is a text · 0c542291
      Bruce Momjian 提交于
      field. cf. Tom Lane's <19021.950544016@sss.pgh.pa.us> 14 Feb hackers
      message.
      
      Cheers,
      
      Patrick Welche
      0c542291
    • B
      I've recently written to pgsql-ports about a problem with PG7.0 on NT · 8fa8f80c
      Bruce Momjian 提交于
      (Subj: [PORTS] initdb problem on NT with 7.0).  Since nobody helped me,
      I had to find out the reson.  The difference between NT and Linux (for
      instance) is that "open( path, O_RDWR );" opens a file in text mode.  So
      sometime less block can be read than required.
      
      I suggest a following patch.  BTW the situation appeared before, see
      hba.c, pqcomm.c and others.
      
      
      Alexei Zakharov
      8fa8f80c
    • T
      Someone (probably me) forgot about handling of typecasts applied to · 9606f362
      Tom Lane 提交于
      parameters.
      9606f362
    • B
      91124a2f
    • B
      Sorting for the inet data type randomly returns the wrong result · 52d39d51
      Bruce Momjian 提交于
      when you have networks with the same prefix, but different netmasks.
      
      This is due to the fact that occassionally there is random
      (uninitialized?)
      data in the extra bits past the point where the netmask cares about
      them.
      
      ie (real data from a real live database):
      
        10.0/10 == 00001010.00100000.00100000.00011000
        10.0/11 == 00001010.00000000.00000000.00000000
                              ^ Bad data, normally never seen
      
      The v4bitncmp() function was only taking one bit length argument so
      it would determine that the networks were different, even though
      they really aren't (and the netmask test wouldn't be used).  This
      ONLY happens if the tuple with the longer bit length is used as the
      ip_bits() for the v4bitncmp call AND there happens to be junk data
      in place in the shorter tuple.  Odd and random, but I saw it happen
      a couple times so...
      
      
      Ryan Mooney
      52d39d51
  4. 07 3月, 2000 1 次提交
  5. 06 3月, 2000 1 次提交
  6. 05 3月, 2000 2 次提交
  7. 03 3月, 2000 4 次提交
  8. 02 3月, 2000 9 次提交
  9. 01 3月, 2000 2 次提交