[BUGS] timeofday()::timestamp - not casting

2002-11-28 Thread Henshall, Stuart - Design & Print
Title: timeofday()::timestamp - not casting From 7.2.3: dpt=> select timeofday()::timestamp;   timeofday --  2002-11-28 11:47:37.06366+00 (1 row) all OK however from 7.3rc2 (on cygwin): dev=# select timeofday()::timestamp; ERROR:  Bad timestamp external r

[BUGS] Bug #824: Problem creating data base !!

2002-11-28 Thread pgsql-bugs
Christian Gonzalez ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description Problem creating data base !! Long Description Recently i tried to create a data base via SSH with an user allowed to do it, but it displays the following messa

[BUGS] Bug #824: Problem creating data base !!

2002-11-28 Thread pgsql-bugs
Christian Gonzalez ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description Problem creating data base !! Long Description Recently i tried to create a data base via SSH with an user allowed to do it, but it displays the following messa

Re: [BUGS] timeofday()::timestamp - not casting

2002-11-28 Thread Tom Lane
"Henshall, Stuart - Design & Print" <[EMAIL PROTECTED]> writes: > dev=# select timeofday()::timestamp; > ERROR: Bad timestamp external representation 'Thu Nov 28 11:26:46.488000 > 2002 GMTST' It works for me. Where in the world is cygwin getting "GMTST" from --- surely that's not a real timezone

Re: [BUGS] timeofday()::timestamp - not casting

2002-11-28 Thread Henshall, Stuart - Design & Print
Title: RE: [BUGS] timeofday()::timestamp - not casting Tom Lane wrote: > "Henshall, Stuart - Design & Print" > <[EMAIL PROTECTED]> writes: >> dev=# select timeofday()::timestamp; >> ERROR:  Bad timestamp external representation 'Thu Nov 28 >> 11:26:46.488000 2002 GMTST' > > It works for me. 

[BUGS] Pg_dump uses up RAM and swap space

2002-11-28 Thread Szabó Roland
Hi! Reading the archives I understand this is a problem of postgres version prior 7.1, and I'm experiencing the very same error as Steve Riley reported last month. I saw that the suggestion was to use 7.2, but I'm not sure you meant dump 7.1 database from 7.1 backend using 7.2 pg_dump. We have ap

[BUGS] Fw: CD

2002-11-28 Thread Monson Marukatat
Hi,     I bought the SQL Weekend Crash Course book with a CD. The problem was, I could not find the folder named "Author" which contain the book material in the CD given. I wrote to you earlier but so far got no response. Please help.   Regards, Monson Marukatat

[BUGS] Memory leak detected

2002-11-28 Thread Diego Zuccato
Hello. I found that strange behaviour: gsbusb=# select g.cod, (select count(*) from scatt where grotta=g.cod) as att, count(*) from grotte g, immagine i, scatt a where i.scattata_in=g.cod group by g.cod, att; NOTICE: PortalHeapMemoryFree: 0x0x8233790 not in alloc set! NOTICE: Buffer Leak: [056]

[BUGS] Fw: CD

2002-11-28 Thread Lee Kindness
Monson, This mailing list and website is for the PostgreSQL database system. It is in no-way releated to the "SQL Weekend Crash Course" book or it's publishers. Perhaps you'd be better to contact the publishers: http://www.wileyeurope.com/ and search for the book title... For general PostgreSQ

Re: [BUGS] Memory leak detected

2002-11-28 Thread Tom Lane
Diego Zuccato <[EMAIL PROTECTED]> writes: > NOTICE: PortalHeapMemoryFree: 0x0x8233790 not in alloc set! I'd suggest updating to a newer version of Postgres. That's got to be 7.0 or older. regards, tom lane ---(end of broadcast)---

Re: [BUGS] Pg_dump uses up RAM and swap space

2002-11-28 Thread Neil Conway
On Wed, 2002-11-27 at 12:13, Szabó Roland wrote: > Reading the archives I understand this is a problem of postgres version > prior 7.1, and I'm experiencing the very same error as Steve Riley > reported last month. I searched the archives but I couldn't find the bug report you're referring to. >

Re: [BUGS] Pg_dump uses up RAM and swap space

2002-11-28 Thread Justin Clift
Hi Roland, Szabó Roland wrote: > > Hi! > > Reading the archives I understand this is a problem of postgres version > prior 7.1, and I'm experiencing the very same error as Steve Riley > reported last month. I saw that the suggestion was to use 7.2, but I'm > not sure you meant dump 7.1 database