Your message dated Tue, 18 Mar 2008 22:17:12 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#358546: fixed in postgresql-8.3 8.3.1-1 has caused the Debian Bug report #358546, regarding failure of pg_ctl start -w -D to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 358546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358546 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: postgresql-7.4 Version: 7.4.12-2 Tags: patch When starting the PostgreSQL server (with "pg_ctl start") with a specific directory (the -D flag), the "wait" code (triggered with the -w option) fails to use the directory to find the Unix socket, and so it fails to connect to the newly-started server. To repeat, create a new database and start a server on it: /usr/lib/postgresql/bin/initdb -D /some/directory Edit /some/directory/postgresql.conf to define unix_socket_directory. (It may be a separate bug that this step is necessary.) /usr/lib/postgresql/bin/pg_ctl start -w -D /some/directory -l /some/directory/postgres.log Note the "failed" error message, even though the server did start. The following simple patch passes the Unix socket directory to psql for the wait check. In PostgreSQL 8, the pg_ctl shell script has been replaced by a C program. I haven't tested it, but from looking at the code in pg_ctl.c, I suspect the same bug is present. Running "start -w" calls test_postmaster_connection(). As with the buggy script, that routine sets only the port and fails to set the host/directory as well. < Stephen --- postgresql-7.4.12/src/bin/pg_ctl/pg_ctl.sh 2004-10-21 20:24:27.000000000 -0400 +++ src/bin/pg_ctl/pg_ctl.sh 2006-03-20 13:31:23.000000000 -0500 @@ -387,20 +387,23 @@ if [ -z "$PGPORT" ];then PGPORT=`sed -ne 's/^[ ]*port[^=]*=[ ]\+\([0-9]\+\).*/\1/p' $CONFFILE 2>/dev/null` if [ -z "$PGPORT" ];then PGPORT="$DEF_PGPORT" fi fi + if [ -z "$PGHOST" ];then + PGHOST=`sed -ne "s/^[ ]*unix_socket_directory[^=]*=[ ]\+'\([^'].*\)'/\1/p" "$CONFFILE" 2>/dev/null` + fi # wait for postmaster to start if [ "$wait" = yes ];then cnt=0 $silence_echo $ECHO_N "waiting for postmaster to start..."$ECHO_C while : do - if "$PGPATH/psql" -p $PGPORT -l >/dev/null 2>&1 + if "$PGPATH/psql" -p $PGPORT -h "$PGHOST" -l >/dev/null 2>&1 then break; else $silence_echo $ECHO_N "."$ECHO_C cnt=`expr $cnt + 1` if [ "$cnt" -gt "$wait_seconds" ];then
--- End Message ---
--- Begin Message ---Source: postgresql-8.3 Source-Version: 8.3.1-1 We believe that the bug you reported is fixed in the latest version of postgresql-8.3, which is due to be installed in the Debian FTP archive: libecpg-compat3_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/libecpg-compat3_8.3.1-1_i386.deb libecpg-dev_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/libecpg-dev_8.3.1-1_i386.deb libecpg6_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/libecpg6_8.3.1-1_i386.deb libpgtypes3_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/libpgtypes3_8.3.1-1_i386.deb libpq-dev_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/libpq-dev_8.3.1-1_i386.deb libpq5_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/libpq5_8.3.1-1_i386.deb postgresql-8.3_8.3.1-1.diff.gz to pool/main/p/postgresql-8.3/postgresql-8.3_8.3.1-1.diff.gz postgresql-8.3_8.3.1-1.dsc to pool/main/p/postgresql-8.3/postgresql-8.3_8.3.1-1.dsc postgresql-8.3_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/postgresql-8.3_8.3.1-1_i386.deb postgresql-8.3_8.3.1.orig.tar.gz to pool/main/p/postgresql-8.3/postgresql-8.3_8.3.1.orig.tar.gz postgresql-client-8.3_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/postgresql-client-8.3_8.3.1-1_i386.deb postgresql-client_8.3.1-1_all.deb to pool/main/p/postgresql-8.3/postgresql-client_8.3.1-1_all.deb postgresql-contrib-8.3_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/postgresql-contrib-8.3_8.3.1-1_i386.deb postgresql-contrib_8.3.1-1_all.deb to pool/main/p/postgresql-8.3/postgresql-contrib_8.3.1-1_all.deb postgresql-doc-8.3_8.3.1-1_all.deb to pool/main/p/postgresql-8.3/postgresql-doc-8.3_8.3.1-1_all.deb postgresql-doc_8.3.1-1_all.deb to pool/main/p/postgresql-8.3/postgresql-doc_8.3.1-1_all.deb postgresql-plperl-8.3_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/postgresql-plperl-8.3_8.3.1-1_i386.deb postgresql-plpython-8.3_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/postgresql-plpython-8.3_8.3.1-1_i386.deb postgresql-pltcl-8.3_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/postgresql-pltcl-8.3_8.3.1-1_i386.deb postgresql-server-dev-8.3_8.3.1-1_i386.deb to pool/main/p/postgresql-8.3/postgresql-server-dev-8.3_8.3.1-1_i386.deb postgresql_8.3.1-1_all.deb to pool/main/p/postgresql-8.3/postgresql_8.3.1-1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt <[EMAIL PROTECTED]> (supplier of updated postgresql-8.3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sat, 15 Mar 2008 18:39:36 +0100 Source: postgresql-8.3 Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 postgresql-8.3 postgresql-client-8.3 postgresql-server-dev-8.3 postgresql-doc-8.3 postgresql-contrib-8.3 postgresql-plperl-8.3 postgresql-plpython-8.3 postgresql-pltcl-8.3 postgresql postgresql-client postgresql-doc postgresql-contrib Architecture: source all i386 Version: 8.3.1-1 Distribution: unstable Urgency: low Maintainer: Martin Pitt <[EMAIL PROTECTED]> Changed-By: Martin Pitt <[EMAIL PROTECTED]> Description: libecpg-compat3 - older version of run-time library for ECPG programs libecpg-dev - development files for ECPG (Embedded PostgreSQL for C) libecpg6 - run-time library for ECPG programs libpgtypes3 - shared library libpgtypes for PostgreSQL 8.3 libpq-dev - header files for libpq5 (PostgreSQL library) libpq5 - PostgreSQL C client library postgresql - object-relational SQL database (latest version) postgresql-8.3 - object-relational SQL database, version 8.3 server postgresql-client - front-end programs for PostgreSQL (latest version) postgresql-client-8.3 - front-end programs for PostgreSQL 8.3 postgresql-contrib - additional facilities for PostgreSQL (latest version) postgresql-contrib-8.3 - additional facilities for PostgreSQL postgresql-doc - documentation for the PostgreSQL database management system postgresql-doc-8.3 - documentation for the PostgreSQL database management system postgresql-plperl-8.3 - PL/Perl procedural language for PostgreSQL 8.3 postgresql-plpython-8.3 - PL/Python procedural language for PostgreSQL 8.3 postgresql-pltcl-8.3 - PL/Tcl procedural language for PostgreSQL 8.3 postgresql-server-dev-8.3 - development files for PostgreSQL 8.3 server-side programming Closes: 358546 469180 470935 Changes: postgresql-8.3 (8.3.1-1) unstable; urgency=low . * New upstream bugfix release: - Repair corner-case bugs in "VACUUM FULL". - Fix misbehavior of foreign key checks involving character or bit columns. - Avoid needless deadlock failures in no-op foreign-key checks. - Fix possible core dump when re-planning a prepared query. - Fix possible failure when re-planning a query that calls an SPI-using function. - Fix failure in row-wise comparisons involving columns of different datatypes. - Fix longstanding "LISTEN"/"NOTIFY" race condition. - Disallow "LISTEN" and "UNLISTEN" within a prepared transaction This was formerly allowed but trying to do it had various unpleasant consequences, notably that the originating backend could not exit as long as an "UNLISTEN" remained uncommitted. - Disallow dropping a temporary table within a prepared transaction This was correctly disallowed by 8.1, but the check was inadvertently broken in 8.2 and 8.3. - Fix rare crash when an error occurs during a query using a hash index. - Fix incorrect comparison of tsquery values. - Fix incorrect behavior of LIKE with non-ASCII characters in single-byte encodings. (Closes: #469180) - Disable xmlvalidate. This function should have been removed before 8.3 release, but was inadvertently left in the source code. It poses a small security risk since unprivileged users could use it to read the first few characters of any file accessible to the server. - Fix memory leaks in certain usages of set-returning functions. - Make encode(bytea, 'escape') convert all high-bit-set byte values into \"nnn" octal escape sequences. This is necessary to avoid encoding problems when the database encoding is multi-byte. This change could pose compatibility issues for applications that are expecting specific results from encode. - Fix input of datetime values for February 29 in years BC. The former coding was mistaken about which years were leap years. . Fix "unrecognized node type" error in some variants of "ALTER OWNER". - Avoid tablespace permissions errors in "CREATE TABLE LIKE INCLUDING INDEXES". - Ensure pg_stat_activity.waiting flag is cleared when a lock wait is aborted. - Fix ecpg problems with arrays. - Fix pg_ctl to correctly extract the postmaster's port number from command-line options. Previously, pg_ctl start -w could try to contact the postmaster on the wrong port, leading to bogus reports of startup failure. (Closes: #358546) - Use "-fwrapv" to defend against possible misoptimization in recent gcc versions (4.3 and later). * debian/postgresql-8.3.init: - Remove erroneous 'S' from Should-Stop. - Require $remote_fs for startup, since postgresql needs /usr. - Thanks to Petter Reinholdtsen! - (Closes: #470935) Files: fca188a2ff1b57f6c1a3b810fedefab5 1191 misc optional postgresql-8.3_8.3.1-1.dsc 6fd12c83f56339ca7ec4bf9c2c6a33f0 13671595 misc optional postgresql-8.3_8.3.1.orig.tar.gz 51ca19404a69acfa2ca18fe3782b8814 55955 misc optional postgresql-8.3_8.3.1-1.diff.gz b77620108f5a2cbf5d6708b4ff266a38 2042340 doc optional postgresql-doc-8.3_8.3.1-1_all.deb 05369d3d86cd92c7c1734bfed955090a 198994 misc optional postgresql_8.3.1-1_all.deb 0a4958f833dde119fbe25e2ef978356d 198970 misc optional postgresql-client_8.3.1-1_all.deb 8f76774f80e64660908054bee2713bc0 198806 doc optional postgresql-doc_8.3.1-1_all.deb b96244880987d8122143077fe6a9fcb0 198858 misc optional postgresql-contrib_8.3.1-1_all.deb e717f7a1fc00f5a796f2acfa093f5169 392908 libdevel optional libpq-dev_8.3.1-1_i386.deb 33616ef73d960cff44369119622d551d 327932 libs optional libpq5_8.3.1-1_i386.deb af962b7dffd1e8f5a9cab077ac8a98a3 226244 libs optional libecpg6_8.3.1-1_i386.deb 15725e269c92136f3c9148b6bf61f2bc 408480 libdevel optional libecpg-dev_8.3.1-1_i386.deb d728c2481afb38f14a95975d754df563 205940 libs optional libecpg-compat3_8.3.1-1_i386.deb 9c71d13bb264c8ade8d6b041330824c5 227188 libs optional libpgtypes3_8.3.1-1_i386.deb 0ab503a94ffe94ebdf8d47736871bf64 5128352 misc optional postgresql-8.3_8.3.1-1_i386.deb 717005fc4f508a29c5e6ba86043fcb16 1597324 misc optional postgresql-client-8.3_8.3.1-1_i386.deb e89eb024f48d2a6ca913b43c1a5c575e 764118 libdevel optional postgresql-server-dev-8.3_8.3.1-1_i386.deb accc7d7698ba51adc310f4b47eaf8366 521030 misc optional postgresql-contrib-8.3_8.3.1-1_i386.deb ac8ef501e5f51d66c9e0b0a6754d8be0 226166 misc optional postgresql-plperl-8.3_8.3.1-1_i386.deb 93271d133e86adf52b43ee379a60fa3a 217050 misc optional postgresql-plpython-8.3_8.3.1-1_i386.deb 096b9f674c8394e54eae45888a7b9f85 216394 misc optional postgresql-pltcl-8.3_8.3.1-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH3ZNADecnbV4Fd/IRAj2EAJ4uBHwineuK541RrXL8BpoS7VWRRgCgvlpo PREGmKY8Xh6ELne0mpndbI0= =/uOr -----END PGP SIGNATURE-----
--- End Message ---
