Re: [BUGS] BUG #5207: unable to start postgresql server services
Well, i changed nothing in my postgresql.conf before the accident.. But, after i try changing value on log_destination from 'stdmsg' into 'csvlog', i got this "2009-11-26 16:07:57 ICTPANIC: could not open control file "global/pg_control": Permission denied" I changed it into 'syslog', i got this FATAL: invalid value for parameter "log_destination": "syslog" I changed it again into 'eventlog', i got this "2009-11-27 15:28:03 ICTPANIC: could not open control file "global/pg_control": Permission denied" again.. i also try to change pg_log folder permissions, but nothing happens.. On 11/26/09, Robert Haas wrote: > On Sat, Nov 21, 2009 at 9:13 AM, denny saviant > wrote: >> >> The following bug has been logged online: >> >> Bug reference: 5207 >> Logged by: denny saviant >> Email address: konohabluefl...@gmail.com >> PostgreSQL version: 8.4.1 >> Operating system: windows xp pro sp3 >> Description: unable to start postgresql server services >> Details: >> >> I installed my postgresql 8.4.1 successfully without any problems. But >> there >> was a problem,the server service won't run. After spending hours of >> searching i postgre mailing list. I able to solve it by following the >> instruction in >> http://archives.postgresql.org/pgsql-admin/2006-05/msg00168.php . >> which is by assigning Log on as local system account in services >> properties. >> And voila, it works.. >> >> couple days later, this kind of trouble come again exactly after i restart >> w3svc service and restart my PC. (i know it after checking the log). >> >> And here's the windows event log that shows the failure.. >> >> Waiting for server startup... >> >> LOG: unrecognized "log_destination" key word: "stdmsg" >> >> FATAL: invalid value for parameter "log_destination": "stdmsg" >> >> Is there anyone know how to solve this? >> I am currently using this postgresql server as my dbms of choice to finish >> my minor project assignment in college. > > Sounds like you have a bad setting for log_destination in your > postgresql.conf file. > > ...Robert > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5216: pgFouine 1.1 not working correctly, when LC_MESSAGES is "es_ES.UTF-8"
On Fri, Nov 27, 2009 at 2:11 AM, Guillaume Smet wrote: > Henrik, > > On Fri, Nov 27, 2009 at 4:15 AM, Henrik Pestano wrote: >> This information can be in two columns. > > Please note that pgsql-bugs mailing list is for PostgreSQL bugs only. > i think what Henrik was proposing is change postgresql's csv format to store the duration and statements values in different columns. Then, pgFouine will have no problem identifying those values no matter the language. i know i agree with the idea, is very ugly to be writing: " like 'duration: %' instead of simply 'duration >= ' -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] psql -1 -f - busted
On Fri, Nov 27, 2009 at 1:42 AM, Peter Eisentraut wrote: > On tor, 2009-11-26 at 22:59 -0500, Robert Haas wrote: >> ISTM that if you run psql with "-f -", you shouldn't expect to get an >> interactive shell. Rather, you should expect psql to do whatever it >> normally does when given -f somefilename, except using stdin rather >> than the file. After all, you could have left out -f altogether if >> you'd wanted the interactive behavior. But then IJWH. > > But by that logic, psql < file should also set interactive mode. Those two cases are not symmetrical. If you're reading from something other than a terminal, you certainly don't want interactive mode. If you ARE reading from a terminal, you might nevertheless want non-interactive mode. And you CERTAINLY might want -1 when reading a pipe, as when you do this: ssh otherhost pg_dump | psql -1 -f - Currently, this silently fails to deliver the expected behavior. ...Robert -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5207: unable to start postgresql server services
On Fri, Nov 27, 2009 at 3:42 AM, Denny Saviant Mohammad wrote: > Well, i changed nothing in my postgresql.conf before the accident. Well, someone or something did, because stdmsg isn't ever a legal value, and it didn't put itself into that file. . > But, after i try changing value on log_destination from 'stdmsg' into > 'csvlog', > i got this "2009-11-26 16:07:57 ICTPANIC: could not open control file > "global/pg_control": Permission denied" This would seem to indicate that either the permissions on the PostgreSQL data directory have been changed, or you're trying to start PostgreSQL under the wrong user account. > I changed it into 'syslog', i got this > FATAL: invalid value for parameter "log_destination": "syslog" > > I changed it again into 'eventlog', i got this "2009-11-27 15:28:03 > ICTPANIC: could not open control file "global/pg_control": Permission > denied" again.. > > i also try to change pg_log folder permissions, but nothing happens.. I would suggest that you post to a different mailing list, such as pgsql-novice or pgsql-general. This mailing list is for bug reports, and it doesn't sound to me like there's a bug here. I would start by setting log_destination = eventlog - since stdmsg is definitely not going to work - and then ask for help on one of those mailing lists fixing your permissions problem. ...Robert -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #5217: (new) error with VB 6.0 SP 6 and psqlODBC 8.4.1
The following bug has been logged online: Bug reference: 5217 Logged by: Martin Email address: searepo...@aol.at PostgreSQL version: 8.4.1 Operating system: M$ Vista (but does not matter) same on XP, ... Description:(new) error with VB 6.0 SP 6 and psqlODBC 8.4.1 Details: works fine with psqlODBC 8.3.4, error with psqlODBC 8.4.1 Sp.CursorType = adOpenDynamic Sp.Open "SELECT field1, False :: boolean as Field2 from test LIMIT 1;", PGSQL_Connection Sp!Field2 = "1" ' < error I can send mylog_3804.log and psqlodbc_3804.log, if someone is interested. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5172: ecpg - cursor with regexp containing '.*/' fails to compile with gcc
On Sat, Nov 07, 2009 at 06:56:36PM +, Viisard wrote: > Description:ecpg - cursor with regexp containing '.*/' fails to Fixed in HEAD and 8.4. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: mes...@jabber.org VfL Borussia! Forca Barca! Go SF 49ers! Use: Debian GNU/Linux, PostgreSQL -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
