Your message dated Thu, 24 Apr 2008 11:01:30 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#474501: /usr/bin/pg_dump: fails due to unrecognized
parameter synchronize_seqscans
has caused the Debian Bug report #474501,
regarding /usr/bin/pg_dump: fails due to unrecognized parameter
synchronize_seqscans
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.)
--
474501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474501
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: postgresql-client-common
Version: 86
Severity: important
File: /usr/bin/pg_dump
I get output like the following when attempting to dump any database:
[EMAIL PROTECTED]:~$ pg_dump test
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: unrecognized configuration
parameter "synchronize_seqscans"
pg_dump: The command was: SET synchronize_seqscans TO off
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.18.xs4.0.1.900.5799 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages postgresql-client-common depends on:
ii debconf [debconf-2.0] 1.5.20 Debian configuration management sy
postgresql-client-common recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Robert,
Robert C. Sheets [2008-04-23 12:06 -0700]:
> Yes, sorry about this. I just discovered a few days ago that a previous
> upgrade had shown no signs of failing, but in fact had not restarted
> postmaster.
Oh, that would indeed be a bug. Can you reproduce it somehow? Playing
with "apt-get install --reinstall postgresql-8.3" or so? (It works
fine for me, but your system might have some local specialities which
make that fail).
> The init script apparently assumed that it had successfully
> stopped the server, when in fact the server hadn't shut down due to some
> long-lived connections.
The init script is actually meant to ensure that the postmaster is
shut down; it calls pg_ctlcluster with --force, which in turn uses
pg_ctl first in fast, then in immediate mode. If even that fails, it
kill -9's the postmaster. This might have failed for you for some reason?
> This led to the running version staying at 8.3RC2 while the version
> visible in the file system was 8.3. Once I convinced postmaster to
> really stop and start, the problem went away.
How did you do that then? Did the long-lived connections just
disappear, or did you apply a bigger hammer?
> I meant to update the bug report, but hadn't gotten around to it. It can
> be closed. Please accept my apology for the bogus bug report. There may
> be an actual bug in the upgrade process, but I haven't managed to
> reproduce it yet.
No need to apologize, I appreciate getting problem reports. Obviously
there is something left to fix here.
Since you cannot reproduce it now, I'm closing this. Once you can
reproduce the 'does not restart' problem, please report back here or
just file a new report.
Thank you!
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
--- End Message ---
