[BUGS] Postgresql is not starting
martin ([EMAIL PROTECTED]) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description Postgresql is not starting Long Description I got to upgrade my linux from 7.0 to 7.1, and since them the posgresql is not starting it's giving me an error: psql: connectDBStart() -- connect() failed: No such file or directory Is the postmaster running at 'localhost' and accepting connections on Unix socket '5432'? What could be wrong Please assist thanks Sample Code I got to upgrade my linux from 7.0 to 7.1, and since them the posgresql is not starting it's giving me an error: psql: connectDBStart() -- connect() failed: No such file or directory Is the postmaster running at 'localhost' and accepting connections on Unix socket '5432'? No file was uploaded with this report ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] Date Conversion Bug
Ayal Leibowitz ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Date Conversion Bug
Long Description
Hi,
I encountered this bug in Postgres version 6.5 to 7.1 and on RedHat Linux versions 6.1
to 7.1.
It's similar or even identical to bugs #208 and #249, but I want to clarify a little
more.
It looks like Postgres refers to the time zone when converting character string to
date type. For example, when I type:
select date('1993-04-02') from xxx;
I get 1993-04-01 for each line in xxx.
My default time zone is GMT+2. If I type: set time zone 'gmt'; before the above query
the result is as expected: 1993-04-02.
To my understanding, date shouldn't be influenced by the time zone, only the time and
timestamp types. This is the reason why the newly version 7.1 "WITHOUT TIME ZONE" type
qualifier does not relate to the date type.
Like specified in #249, it happens only on the switch from normal to daylight saving
time.
Ayal Leibowitz,
Modelity Technologies.
Sample Code
select date('1993-04-02') from xxx;
results with 1993-04-01 in psql.
No file was uploaded with this report
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
[BUGS] Cygwin: postgres.exe exits with "*** recreate_mmaps_after_fork_failed" message
David Polberger ([EMAIL PROTECTED]) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description Cygwin: postgres.exe exits with "*** recreate_mmaps_after_fork_failed" message Long Description (Note that this bug might be considered a duplicate of #188). I have installed PostgreSQL v7.1 on a system running Windows 2000 Service Pack 1 with a recent Cygwin installation. I have followed the installation instructions to the letter, both in INSTALL and doc/FAQ_MSWIN. ./configure, make, make install and initdb work fine. Then I try to execute the following command: /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data >logfile 2>&1 & Per the instructions in INSTALL. postmaster.exe is loaded in the background, as expected. Approximately one second later, I get the following error message: $ C:\Utility\CygWin\usr\local\pgsql\bin\postgres.exe: *** recreate_mmaps_after_fork_failed Note that I haven't done anything unusual; I have followed the installation instructions to the letter, as mentioned. Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] debug_level 0 does not stop debug messages
JP ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description debug_level 0 does not stop debug messages Long Description I'm trying to silence the annoying output generated by vacuum. I've tried both command line options (-d 0, -S (with syslog enabled)) and postgresql.conf (debug_level = 0, silent_mode = 1). Setting debug level to 0 should silence these messages, but still let errors through. Setting debug level higher seems to generate more output, which is great. just be nice if the vacuum output were at level 3 or greater. Platform: OpenBSD 2.8 (i386) PG Version: 7.1 Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] Inheritance of functions shows unexpected behaviour
[EMAIL PROTECTED] writes: > Inheritance of functions shows unexpected behaviour I agree, plpgsql is doing the wrong thing here. Fix committed for 7.1.1. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] debug_level 0 does not stop debug messages
Hi, This might sound weird, but try " pg_ctl start -o '-d0' Include any other options you need of course too. The point is not having a space between the -d and the 0. This fixes things for me when I have the default startup options different, but need logging off for a while. Regards and best wishes, Justin Clift [EMAIL PROTECTED] wrote: > > JP ([EMAIL PROTECTED]) reports a bug with a severity of 2 > The lower the number the more severe it is. > > Short Description > debug_level 0 does not stop debug messages > > Long Description > I'm trying to silence the annoying output generated by vacuum. I've > tried both command line options (-d 0, -S (with syslog enabled)) and > postgresql.conf (debug_level = 0, silent_mode = 1). Setting debug > level to 0 should silence these messages, but still let errors through. Setting >debug level higher seems to generate more output, which is great. just be nice if >the vacuum output were at level 3 or > greater. > > Platform: OpenBSD 2.8 (i386) > PG Version: 7.1 > > Sample Code > > No file was uploaded with this report > > ---(end of broadcast)--- > TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] Date Conversion Bug
Ayal Leibowitz ([EMAIL PROTECTED]) writes:
> I encountered this bug in Postgres version 6.5 to 7.1 and on RedHat Linux versions
>6.1 to 7.1.
Several of the developers have tried to reproduce this bug, with no
success.
> select date('1993-04-02') from xxx;
> I get 1993-04-01 for each line in xxx.
> My default time zone is GMT+2.
Exactly how do you set the time zone? What does "SHOW TIMEZONE" show?
What do you get from
select timestamp('1993-04-01');
select timestamp('1993-04-02');
select timestamp('1993-04-03');
> Like specified in #249, it happens only on the switch from normal to
> daylight saving time.
One reason I'm so interested in your timezone is that 1993-04-02 is not
a DST transition day in any timezone that I know about. In Europe, DST
transitions happen in the last week of March, never in April, according
to the references I can find. In the USA, we do have transitions in
April, but the transition day in 1993 was 04-04.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
[BUGS] Dates and times (and timestamps) don't behave as expected
Bob Soeters ([EMAIL PROTECTED]) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description Dates and times (and timestamps) don't behave as expected Long Description For the most part, I get wrong results when using timestamps and other date or time types and functions. This is devastating, since I rely on timestamps to get some functionality covered. My problem isn't very different from the ones already described, so I'll skip the description. Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Re: [BUGS] Dates and times (and timestamps) don't behave as expected
[EMAIL PROTECTED] writes: > My problem isn't very different from the ones already described, so I'll skip the >description. Why are you bothering to clog our inboxes with a completely information-free complaint? As you know if you've been following these bug reports, none of the developers have been able to reproduce any such problem (at least not in 7.1). We need information about exactly what you're doing, exactly what platform you're doing it on, exactly what timezone definition you're using, etc etc. Nothing will get fixed otherwise. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
