[BUGS] bitfromint4() in v7.2.3 to bit() in v8.1?
Hi,
In version 7.2.3 this works fine:
select substring(bitfromint4(cast (-2^31 + 22 as int4)), 1, 32);
and now I'm porting the legacy code, that this line is part of, to version
8.1 but am having no luck updating it - have tried something like:
select substring(bit(cast (-2^31 + 22 as int4)), 1, 32);
and
select substring("bit"(cast (-2^31 + 22 as int4)), 1, 32);
and
select substring(1::"bit"(cast (-2^31 + 22 as int4)), 1, 32);
with no luck.
How can this be solved?
/Björn
[BUGS] BUG #4765: GIST box Segfaulting on Inserts
The following bug has been logged online: Bug reference: 4765 Logged by: Paolo Saul Email address: paolo.s...@telogis.com PostgreSQL version: 8.3.5 Operating system: RHEL5 x64 Description:GIST box Segfaulting on Inserts Details: We have a table with GIST indexes on a box. Its throwing segfaults with a certain set of box data. To recreate: FILE NEEDED: xx.sql Where can I attach this? Its 47MB. SQL: CREATE TABLE wre_xx ( id oid, geom box ); RUN: psql -U postgres -f xx.sql OUTPUT: psql:xx.sql:230203: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. psql:xx.sql:230203: connection to server was lost LOG: [13844]2009-04-21 05:22:58.606 GMT 0 : LOG: 0: server process (PID 12363) was terminated by signal 11: Segmentation fault TOP OF STACK: (gdb) bt #0 0x0065255f in DirectFunctionCall2 () #1 0x00454c29 in gist_box_picksplit () #2 0x00651cdf in FunctionCall2 () #3 0x00455582 in gistSplitByKey () #4 0x0044c8f5 in gistSplit () #5 0x0044c99b in gistSplit () #6 0x0044c99b in gistSplit () #7 0x0044c99b in gistSplit () #8 0x0044c99b in gistSplit () #9 0x0044c99b in gistSplit () #10 0x0044c99b in gistSplit () #16356 0x0044c99b in gistSplit () #16357 0x0044c99b in gistSplit () #16358 0x0044d2c7 in gistmakedeal () #16359 0x0044db2b in ?? () #16360 0x0044def5 in gistinsert () #16361 0x0065197c in FunctionCall6 () #16362 0x0046489f in index_insert () #16363 0x00522635 in ExecInsertIndexTuples () #16364 0x0051a0db in ExecutorRun () #16365 0x005aed84 in ?? () #16366 0x005aefa4 in ?? () #16367 0x005af7ca in PortalRun () #16368 0x005ac748 in PostgresMain () #16369 0x00582907 in ?? () #16370 0x0058358b in PostmasterMain () #16371 0x0053c4de in main () If you need the file, Just tell me where to upload it. Regards, Paolo Saul Telogis.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] Segfaults When Inserting into a Geom Index
Hi Everyone, We have a Database ( 8.3.5) on RHEL5 x64. It recently ran into Segmentation Faults when inserting rows over a Geom Index. This happened several times this last weekend. The fix was to drop or reindex it. We have set it to dump core at the moment. Any insights into this? Thanks, Jean Paolo Saul Telogis.com
[BUGS] BUG #4767: create operator - negator doesn't work
The following bug has been logged online: Bug reference: 4767 Logged by: fduerr Email address: fdu...@gmx.de PostgreSQL version: 8.3.x 8.4.b1 Operating system: Debian Lenny Description:create operator - negator doesn't work Details: Hi, my apologies beforehand in case i'm just too stupid to understand the documentation... i understand, that the operator's negator argument specifies the operator that, when applied with the same operands, yields the inverted result. So thats what i did: CREATE OR REPLACE FUNCTION eq_int_bool(INTEGER, BOOLEAN) RETURNS BOOLEAN AS 'SELECT CAST($1 AS BOOLEAN)=$2;' LANGUAGE SQL IMMUTABLE; CREATE OPERATOR = ( LEFTARG=INTEGER, RIGHTARG=BOOLEAN, PROCEDURE=eq_int_bool, COMMUTATOR= = , NEGATOR= <> ); And thats, what i got: SELECT 1=false; ?column? -- f (1 row) SELECT 1<>false; 8.3.x: ERROR: cache lookup failed for function 0 8.4b1: ERROR: operator is only a shell: integer <> boolean The workaround is, of course, to define an operator with '<>' as commutator that returns the negated result. Still i wonder: is it me, the documentation or pg? -- 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 #4767: create operator - negator doesn't work
On Tuesday 21 April 2009 14:04:01 fduerr wrote: > CREATE OR REPLACE FUNCTION eq_int_bool(INTEGER, BOOLEAN) RETURNS BOOLEAN AS > 'SELECT CAST($1 AS BOOLEAN)=$2;' LANGUAGE SQL IMMUTABLE; > CREATE OPERATOR = ( > LEFTARG=INTEGER, > RIGHTARG=BOOLEAN, > PROCEDURE=eq_int_bool, > COMMUTATOR= = , > NEGATOR= <> > ); > > And thats, what i got: > > SELECT 1=false; > ?column? > -- > f > (1 row) > > SELECT 1<>false; > 8.3.x: ERROR: cache lookup failed for function 0 > 8.4b1: ERROR: operator is only a shell: integer <> boolean > > The workaround is, of course, to define an operator with '<>' as commutator > that returns the negated result. Still i wonder: is it me, the > documentation or pg? What you did above is to specify which operator is the negator of =. But you still need to create that operator; it is not created automatically. -- 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 #4769: xmlconcat produces invalid xml values -> data corruption
The following bug has been logged online:
Bug reference: 4769
Logged by: Arjen Nienhuis
Email address: a.g.nienh...@gmail.com
PostgreSQL version: 8.3.7
Operating system: Ubuntu 8.10 and 9.04
Description:xmlconcat produces invalid xml values -> data corruption
Details:
'' is a valid xml document but not a valid xml
fragment. xmlconcat does not check for this:
SELECT xmlconcat('foo', xmlparse(DOCUMENT ''));
xmlconcat
---
foo
The result is an invalid xml value that can end up in a table.
==
=> SELECT version();
version
-
PostgreSQL 8.3.7 on x86_64-pc-linux-gnu, compiled by GCC gcc-4.3.real
(Ubuntu 4.3.3-5ubuntu4) 4.3.3
(1 row)
libxml2 version is 2.6.32.dfsg-5ubuntu4
=
I tried to test this with 8.4 but the ubuntu ppa has depency problems.
--
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 #4766: i cant setup a program
The following bug has been logged online: Bug reference: 4766 Logged by: Robert Email address: robb...@rambler.ru PostgreSQL version: 8.3.7-1 Operating system: Windows XP Professional Description:i cant setup a program Details: Installation directory -> next Data directory -> next i got the message: Error The existing data directory (Date/time setting: floating-point numbers) is not compatible with this server (Date/time setting: 64-bit integers) -- 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 #4768: FATAL:could not reattach to shared memory:487
The following bug has been logged online: Bug reference: 4768 Logged by: grouvi Email address: g...@sylob.com PostgreSQL version: 8.3.7 Operating system: Windows 2008 x64 Description:FATAL:could not reattach to shared memory:487 Details: Symptoms: My DB update scripts crashes with the following error message FATAL: could not reattach to shared memory (key=288, addr=0202): 487 The problem occurs with both autovacuum turned on or off. Configuration: -> PostgreSQL 8.3.7 ->Windows 2008 64 bits. It is a normal install. I have no antivirus nor Firewall. There is the Windows Firewall but the problem still occurs while it is turned off. Thanks for help. Here is my full postgresql.conf # - # PostgreSQL configuration file # - # # This file consists of lines of the form: # # name = value # # (The "=" is optional.) Whitespace may be used. Comments are introduced with # "#" anywhere on a line. The complete list of parameter names and allowed # values can be found in the PostgreSQL documentation. # # The commented-out settings shown in this file represent the default values. # Re-commenting a setting is NOT sufficient to revert it to the default value; # you need to reload the server. # # This file is read on server startup and when the server receives a SIGHUP # signal. If you edit the file on a running system, you have to SIGHUP the # server for the changes to take effect, or use "pg_ctl reload". Some # parameters, which are marked below, require a server shutdown and restart to # take effect. # # Any parameter can also be given as a command-line option to the server, e.g., # "postgres -c log_connections=on". Some paramters can be changed at run time # with the "SET" SQL command. # # Memory units: kB = kilobytes MB = megabytes GB = gigabytes # Time units:ms = milliseconds s = seconds min = minutes h = hours d = days #--- --- # FILE LOCATIONS #--- --- # The default values of these variables are driven from the -D command-line # option or PGDATA environment variable, represented here as ConfigDir. #data_directory = 'ConfigDir'# use data in another directory # (change requires restart) #hba_file = 'ConfigDir/pg_hba.conf'# host-based authentication file # (change requires restart) #ident_file = 'ConfigDir/pg_ident.conf'# ident configuration file # (change requires restart) # If external_pid_file is not explicitly set, no extra PID file is written. #external_pid_file = '(none)'# write an extra PID file # (change requires restart) #--- --- # CONNECTIONS AND AUTHENTICATION #--- --- # - Connection Settings - listen_addresses = '*'# what IP address(es) to listen on; # comma-separated list of addresses; # defaults to 'localhost', '*' = all # (change requires restart) port = 5432# (change requires restart) max_connections = 200# 200 pour éviter des "too many clients already" # Note: Increasing max_connections costs ~400 bytes of shared memory per # connection slot, plus lock space (see max_locks_per_transaction). You might # also need to raise shared_buffers to support more connections. #superuser_reserved_connections = 3# (change requires restart) #unix_socket_directory = ''# (change requires restart) #unix_socket_group = ''# (change requires restart) #unix_socket_permissions = 0777# begin with 0 to use octal notation # (change requires restart) #bonjour_name = ''# defaults to the computer name # (change requires restart) # - Security and Authentication - #authentication_timeout = 1min# 1s-600s #ssl = off# (change requires restart) #ssl_ciphers = 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH'# allowed SSL ciphers # (change requires restart) #password_encryption = on #db_user_namespace = off # Kerberos and GSSAPI #krb_server_keyfile = ''# (change requires restart) #krb_srvname = 'postgres'# (change requires restart, Kerberos only) #krb_server_hostname = ''# empty string matches any keytab entry # (change requires restart, Kerberos only) #krb_caseins_users = off# (change requires restart) #krb_realm = '' # (change requires restart) # - TCP Keepalives - # see "man 7 tcp" for details #tcp_keepalives_idle = 0# TCP_KEEPIDLE, in seconds; # 0 selects the system default #tcp_keepalives_interval = 0# TCP_KEEPINTVL
Re: [BUGS] bitfromint4() in v7.2.3 to bit() in v8.1?
=?ISO-8859-1?B?Qmr2cm4g3vNyIErzbnNzb24=?= writes: > In version 7.2.3 this works fine: > select substring(bitfromint4(cast (-2^31 + 22 as int4)), 1, 32); > and now I'm porting the legacy code, that this line is part of, to version > 8.1 but am having no luck updating it - have tried something like: Use a cast, eg regression=# select cast (-2^31 + 22 as int4)::bit(32); bit -- 10010110 (1 row) regards, tom lane -- 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 #4768: FATAL:could not reattach to shared memory:487
This is a known problem. I think stoping/starting the server will fix it. We hope to find the cause soon. --- grouvi wrote: > > The following bug has been logged online: > > Bug reference: 4768 > Logged by: grouvi > Email address: g...@sylob.com > PostgreSQL version: 8.3.7 > Operating system: Windows 2008 x64 > Description:FATAL:could not reattach to shared memory:487 > Details: > > Symptoms: > My DB update scripts crashes with the following error message > FATAL: could not reattach to shared memory (key=288, addr=0202): 487 > The problem occurs with both autovacuum turned on or off. > > > Configuration: > -> PostgreSQL 8.3.7 > ->Windows 2008 64 bits. > It is a normal install. > I have no antivirus nor Firewall. > There is the Windows Firewall but the problem still occurs while it is > turned off. > > > > Thanks for help. > > > Here is my full postgresql.conf > > # - > # PostgreSQL configuration file > # - > # > # This file consists of lines of the form: > # > # name = value > # > # (The "=" is optional.) Whitespace may be used. Comments are introduced > with > # "#" anywhere on a line. The complete list of parameter names and allowed > # values can be found in the PostgreSQL documentation. > # > # The commented-out settings shown in this file represent the default > values. > # Re-commenting a setting is NOT sufficient to revert it to the default > value; > # you need to reload the server. > # > # This file is read on server startup and when the server receives a SIGHUP > # signal. If you edit the file on a running system, you have to SIGHUP the > # server for the changes to take effect, or use "pg_ctl reload". Some > # parameters, which are marked below, require a server shutdown and restart > to > # take effect. > # > # Any parameter can also be given as a command-line option to the server, > e.g., > # "postgres -c log_connections=on". Some paramters can be changed at run > time > # with the "SET" SQL command. > # > # Memory units: kB = kilobytes MB = megabytes GB = gigabytes > # Time units:ms = milliseconds s = seconds min = minutes h = hours d = > days > > > #--- > --- > # FILE LOCATIONS > #--- > --- > > # The default values of these variables are driven from the -D command-line > # option or PGDATA environment variable, represented here as ConfigDir. > > #data_directory = 'ConfigDir'# use data in another directory > # (change requires restart) > #hba_file = 'ConfigDir/pg_hba.conf'# host-based authentication file > # (change requires restart) > #ident_file = 'ConfigDir/pg_ident.conf'# ident configuration file > # (change requires restart) > > # If external_pid_file is not explicitly set, no extra PID file is written. > #external_pid_file = '(none)'# write an extra PID file > # (change requires restart) > > > #--- > --- > # CONNECTIONS AND AUTHENTICATION > #--- > --- > > # - Connection Settings - > > listen_addresses = '*'# what IP address(es) to listen on; > # comma-separated list of addresses; > # defaults to 'localhost', '*' = all > # (change requires restart) > port = 5432# (change requires restart) > max_connections = 200# 200 pour ??viter des "too many clients already" > # Note: Increasing max_connections costs ~400 bytes of shared memory per > # connection slot, plus lock space (see max_locks_per_transaction). You > might > # also need to raise shared_buffers to support more connections. > #superuser_reserved_connections = 3# (change requires restart) > #unix_socket_directory = ''# (change requires restart) > #unix_socket_group = ''# (change requires restart) > #unix_socket_permissions = 0777# begin with 0 to use octal notation > # (change requires restart) > #bonjour_name = ''# defaults to the computer name > # (change requires restart) > > # - Security and Authentication - > > #authentication_timeout = 1min# 1s-600s > #ssl = off# (change requires restart) > #ssl_ciphers = 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH'# allowed SSL ciphers > # (change requires restart) > #password_encryption = on > #db_user_namespace = off > > # Kerberos and GSSAPI > #krb_server_keyfile = ''# (change requires restart) > #krb_srvname = 'postgres'# (change requires restart, Kerberos only) > #krb_server_ho
Re: [BUGS] BUG #4765: GIST box Segfaulting on Inserts
"Paolo Saul" writes: > [ apparently infinite recursion in gistSplit ] This may be the same problem identified a couple of weeks ago. Does this patch fix it? http://archives.postgresql.org/pgsql-committers/2009-04/msg00076.php regards, tom lane -- 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 #4768: FATAL:could not reattach to shared memory:487
Ghislain ROUVIGNAC wrote: > Thanks for your answer. > > > Stoping/starting the server does not solve the problem. > It reappears quickly. > > As a work around I still run my DB on Linux Red Hat with Postgres 8.1, but i > would like to move to the new Windows 2008 server. > > > How can I know when a fix will be released ? Uh, have you tried rebooting the server? Here is our TODO item: Diagnose problem where shared memory can sometimes not be attached by postmaster children * FATAL: could not reattach to shared memory (Win32) -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- 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 #4768: FATAL:could not reattach to shared memory:487
Bruce Momjian wrote: > Ghislain ROUVIGNAC wrote: > > Thanks for your answer. > > > > > > Stoping/starting the server does not solve the problem. > > It reappears quickly. > > > > As a work around I still run my DB on Linux Red Hat with Postgres 8.1, but i > > would like to move to the new Windows 2008 server. > > > > > > How can I know when a fix will be released ? > > Uh, have you tried rebooting the server? Here is our TODO item: > > Diagnose problem where shared memory can sometimes not be attached by > postmaster children > > * FATAL: could not reattach to shared memory (Win32) Oh, sorry, here is the URL describing the problem: http://archives.postgresql.org/pgsql-general/2007-08/msg01377.php -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- 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 #4768: FATAL:could not reattach to shared memory:487
Ghislain ROUVIGNAC wrote: > I didn't tried to reboot the windows server. > I'll try it when i will have time. > > > Thank you for the references to the problem. OK, let us know if it does not fix the problem. As you can see this bug has been around for a while. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- 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 #4768: FATAL:could not reattach to shared memory:487
Thanks for your answer. Stoping/starting the server does not solve the problem. It reappears quickly. As a work around I still run my DB on Linux Red Hat with Postgres 8.1, but i would like to move to the new Windows 2008 server. How can I know when a fix will be released ? -Message d'origine- De : Bruce Momjian [mailto:br...@momjian.us] Envoyé : mardi 21 avril 2009 16:14 À : grouvi Cc : pgsql-bugs@postgresql.org Objet : Re: [BUGS] BUG #4768: FATAL:could not reattach to shared memory:487 This is a known problem. I think stoping/starting the server will fix it. We hope to find the cause soon. --- grouvi wrote: > > The following bug has been logged online: > > Bug reference: 4768 > Logged by: grouvi > Email address: g...@sylob.com > PostgreSQL version: 8.3.7 > Operating system: Windows 2008 x64 > Description:FATAL:could not reattach to shared memory:487 > Details: > > Symptoms: > My DB update scripts crashes with the following error message > FATAL: could not reattach to shared memory (key=288, addr=0202): 487 > The problem occurs with both autovacuum turned on or off. > > > Configuration: > -> PostgreSQL 8.3.7 > ->Windows 2008 64 bits. > It is a normal install. > I have no antivirus nor Firewall. > There is the Windows Firewall but the problem still occurs while it is > turned off. > > > > Thanks for help. > > > Here is my full postgresql.conf > > # - > # PostgreSQL configuration file > # - > # > # This file consists of lines of the form: > # > # name = value > # > # (The "=" is optional.) Whitespace may be used. Comments are introduced > with > # "#" anywhere on a line. The complete list of parameter names and allowed > # values can be found in the PostgreSQL documentation. > # > # The commented-out settings shown in this file represent the default > values. > # Re-commenting a setting is NOT sufficient to revert it to the default > value; > # you need to reload the server. > # > # This file is read on server startup and when the server receives a SIGHUP > # signal. If you edit the file on a running system, you have to SIGHUP the > # server for the changes to take effect, or use "pg_ctl reload". Some > # parameters, which are marked below, require a server shutdown and restart > to > # take effect. > # > # Any parameter can also be given as a command-line option to the server, > e.g., > # "postgres -c log_connections=on". Some paramters can be changed at run > time > # with the "SET" SQL command. > # > # Memory units: kB = kilobytes MB = megabytes GB = gigabytes > # Time units:ms = milliseconds s = seconds min = minutes h = hours d = > days > > > #--- > --- > # FILE LOCATIONS > #--- > --- > > # The default values of these variables are driven from the -D command-line > # option or PGDATA environment variable, represented here as ConfigDir. > > #data_directory = 'ConfigDir'# use data in another directory > # (change requires restart) > #hba_file = 'ConfigDir/pg_hba.conf'# host-based authentication file > # (change requires restart) > #ident_file = 'ConfigDir/pg_ident.conf'# ident configuration file > # (change requires restart) > > # If external_pid_file is not explicitly set, no extra PID file is written. > #external_pid_file = '(none)'# write an extra PID file > # (change requires restart) > > > #--- > --- > # CONNECTIONS AND AUTHENTICATION > #--- > --- > > # - Connection Settings - > > listen_addresses = '*'# what IP address(es) to listen on; > # comma-separated list of addresses; > # defaults to 'localhost', '*' = all > # (change requires restart) > port = 5432# (change requires restart) > max_connections = 200# 200 pour éviter des "too many clients already" > # Note: Increasing max_connections costs ~400 bytes of shared memory per > # connection slot, plus lock space (see max_locks_per_transaction). You > might > # also need to raise shared_buffers to support more connections. > #superuser_reserved_connections = 3# (change requires restart) > #unix_socket_directory = ''# (change requires restart) > #unix_socket_group = ''# (change requires restart) > #unix_socket_permissions = 0777# begin with 0 to use octal notation > # (change requires restart) > #bonjour_name = ''# defaults to the computer name > # (change requires restart) >
[BUGS] Automatic login deactivated in Windows 7
Hi, I want to report a little bug I've encountered in Windows 7... With the latest version 8.3.7 finally it install and works fine, except for the automatic login that it deactivated (in WinXP and WinVista it doesn't)... For example: if I have only one user on my pc, without password and with automatic login, after I install PostgreSQL with windows installer, after I reboot, I have to click on my user image for login... Naturally there is a workaround to restore the autologin (from cmd "control userpasswords2" and check it), but if I can fix them, it's a little good news... Thanks you...
[BUGS] BUG #4770: Error initializing slon in command line and hence running Slony
The following bug has been logged online: Bug reference: 4770 Logged by: Quincy Email address: qj_qwe...@hotmail.com PostgreSQL version: 8.3.7 Operating system: Windows Vista Description:Error initializing slon in command line and hence running Slony Details: Hello everyone, I tried to find a solution for a few days now on an error that kept occuring after trying to install & run slony-1 immediately after installing postgres DB system. What kept on happening after installing slony-1 via the stackbuilder and then testing the slon service in command line was an error containing the following: "The procedure entry point libiconv_set_relocation_prefix could not be located in the dynamic link library libiconv-2.dll". Windows log had this in the error report: libiconv-2.dll!libiconv_set_relocation_prefix It took a while to realise that when I install slony-1, it creates and overwrites the file libiconv -2.dll found in the bin of the postgres installation folder. The only difference between the files are their size & date created. What I found as a work around was to first stop the posgres service, then use the libiconv-2.dll (947kb) originally installed by postgres and by either renaming or moving that file to then overwrite the libiconv-2.dll created by the slony installation. Meaning, the file that should remain for everything to work is the original libiconv-2.dll (947kb) created by the postgres installation. If this error was already addressed please let me know as I really was trying to find a solution to the above problem and could not find one suitable. -- 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 #4770: Error initializing slon in command line and hence running Slony
On Tue, Apr 21, 2009 at 8:22 PM, Quincy wrote: > > What I found as a work around was to first stop the posgres service, then > use the libiconv-2.dll > > (947kb) originally installed by postgres and by either renaming or moving > that file to then > > overwrite the libiconv-2.dll created by the slony installation. Meaning, the > file that should remain > > for everything to work is the original libiconv-2.dll (947kb) created by the > postgres installation. Can you try this installer update please? http://developer.pgadmin.org/~dpage/Slony_I_PG83-1.2.15.msi It should be installed into the server directory - for example, C:\Program Files\PostgreSQL\8.3. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com -- 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 #4771: Postgres wont start
The following bug has been logged online: Bug reference: 4771 Logged by: Christine Penner Email address: christi...@telus.net PostgreSQL version: 8.3.7 Operating system: Vista Description:Postgres wont start Details: I have had Postgres running and working on the computer for about a month. A week ago I started and realized that the Postgres service was not started. I started it and it worked fine. Today I started up and again Postgres has not started. I have tried again and again to start it but it won't start. I have restarted my computer 3 times, shut down programs running that may interfere but still nothing. I can't find a log file that will give me more info on why it won't start. -- 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 #4771: Postgres wont start
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christine Penner wrote: > The following bug has been logged online: > > Bug reference: 4771 > Logged by: Christine Penner > Email address: christi...@telus.net > PostgreSQL version: 8.3.7 > Operating system: Vista > Description:Postgres wont start > Details: > > I have had Postgres running and working on the computer for about a month. A > week ago I started and realized that the Postgres service was not started. I > started it and it worked fine. Today I started up and again Postgres has not > started. I have tried again and again to start it but it won't start. I have > restarted my computer 3 times, shut down programs running that may interfere > but still nothing. > > I can't find a log file that will give me more info on why it won't start. > what is the Error you are getting ? go to bin folder of postgres and try to start using pg_ctl like :- pg_ctl -D c:/postgres/8.3/...path upto data folder START -- regards,tushar http://webeatoracle.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFJ7q9LfQNodY2PIRoRArjqAKCIfLk/392qYIn+cQY7iy23IPXNxQCgtetG 8Q7KHYTH/gcd3+WSQnCd/Zw= =7r7H -END PGP SIGNATURE- -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
