Re: [BUGS] 7.1 released on 2000-09-01?

> Hi, > > [[EMAIL PROTECTED] doesn't seem to accept this report, > so I send it to you.] > > The PostgreSQL Administrator's Guide says in the release notes: > > Release 7.1 > Release date 2000-09-01. > > I wish that was true! > > Unfortunately, everwhere else on the site the latest release is

Re: [BUGS] postgres in 'C' - can't get started

"Graeme Stobbart" <[EMAIL PROTECTED]> writes: > /usr/lib/libpq.a (fe-auth.a): In function `pg_password_sendauth`: > fe-auth.o(.text+0x30): undefined reference to `crypt` On some platforms you need to specify -lcrypt explicitly when linking. (Sometimes crypt() is in the standard library, sometimes

[BUGS] 7.1 released on 2000-09-01?

Hi, [[EMAIL PROTECTED] doesn't seem to accept this report, so I send it to you.] The PostgreSQL Administrator's Guide says in the release notes: Release 7.1 Release date 2000-09-01. I wish that was true! Unfortunately, everwhere else on the site the latest release is 7.0.3. See for your self

[BUGS] postgres in 'C' - can't get started

Red Hat 7, Vanilla install postgres from RPM's   Create very simple program to open/close (cut down vsn of example 1)   Compile using libpq.a   Follwing error...   /usr/lib/libpq.a (fe-auth.a): In function `pg_password_sendauth`: fe-auth.o(.text+0x30): undefined reference to `crypt`   New

[BUGS] Python interface with CFLAGS

Hi. uname -a SunOS iridium 5.6 Generic_105181-20 sun4u sparc SUNW,Ultra-5_10 python Python 2.0b1 (#5, Sep 12 2000, 13:36:09) [GCC 2.95.2 19991024 (release)] on sunos5 I use cvs version, after update I tried: make distclean; configure --with-tcl --with-perl --with-python --with-openssl --with-C

[BUGS] Problem...

Hi, I am installing Postgres 7.0 on Windows NT workstation When I run the "psql -h localhost template1" command I get the segmentation fault(core dump) Can anyone help me with this I have attached the stackdump file Praveen ___

Re: [BUGS] inability to restore infinity values via psql or pg_restore

[EMAIL PROTECTED] writes: > inability to restore infinity values via psql or pg_restore I don't think this has anything to do with a dump/restore problem. What it is is a problem with dealing with overflow in timestamp calculations. In current sources: regression=# select timestamp 'infinity' -

[BUGS] inability to restore infinity values via psql or pg_restore

Thomas F. OConnell ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description inability to restore infinity values via psql or pg_restore Long Description i am currently attempting to use infinite interval values in various tables in my