[BUGS] Fwd: Bug#358546: failure of pg_ctl start -w -D

2006-03-26 Thread Martin Pitt
Hi PostgreSQL developers, the bug report below was recently sent to Debian. The details and my reply are at http://bugs.debian.org/358546, the executive summary is: pg_ctl's -w option does not honour postgresql.conf's unix_socket_directory configuration (and neither $PGHOST). Thanks, Martin ---

[BUGS] Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]

2006-03-26 Thread Martin Pitt
Hi PostgreSQL developers, FYI, this was recently sent to the ancient old Debian bug report 'Postmaster ignores SIGPIPE'. [1] It seems that this was introduced way back in 1997 in [2], but withouth a sufficient explanation why SIGPIPE isn't properly handled instead of just ignored. The bug trail i

Re: [BUGS] Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]

2006-03-26 Thread Tom Lane
Martin Pitt <[EMAIL PROTECTED]> writes: > The bug trail in [1] contains a followup from Tom that ignoring > SIGPIPE is specifically intended. Is there any document which states > the reason for that? Allowing SIGPIPE to kill the backend is completely infeasible, as the backend would be unable to r

Re: [BUGS] Fwd: Bug#358546: failure of pg_ctl start -w -D

2006-03-26 Thread Tom Lane
Martin Pitt <[EMAIL PROTECTED]> writes: > the bug report below was recently sent to Debian. The details and my > reply are at http://bugs.debian.org/358546, the executive summary is: > pg_ctl's -w option does not honour postgresql.conf's > unix_socket_directory configuration (and neither $PGHOST).

Re: [BUGS] Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]

2006-03-26 Thread Peter Eisentraut
Tom Lane wrote: > Allowing SIGPIPE to kill the backend is completely infeasible, as the > backend would be unable to release locks etc before dying. So the upshot is really not that ignoring SIGPIPE is specifically intended as the optimal solution but that writing a proper cleanup handler for SI

[BUGS] BUG #2359: silent Installer for Postgresql 8.1.3 ignores BASEDIR

2006-03-26 Thread tao.shen
The following bug has been logged online: Bug reference: 2359 Logged by: tao.shen Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.3 Operating system: winXP Description:silent Installer for Postgresql 8.1.3 ignores BASEDIR Details: Silent Installer for Postg

Re: [BUGS] BUG #2357: docs for mod() are wrong

2006-03-26 Thread Philip Crotwell
On Mar 24, 2006, at 4:39 PM, Tom Lane wrote: "Philip Crotwell" <[EMAIL PROTECTED]> writes: It would be nice if mod could directly take a double, Given the inherent approximate nature of float arithmetic, I'm not sure this makes a lot of sense. How often do you really do modulo on floats?

[BUGS] Fwd: Bug#358546: failure of pg_ctl start -w -D

2006-03-26 Thread Martin Pitt
Hi PostgreSQL developers, the bug report below was recently sent to Debian. The details and my reply are at http://bugs.debian.org/358546, the executive summary is: pg_ctl's -w option does not honour postgresql.conf's unix_socket_directory configuration (and neither $PGHOST). Thanks, Martin ---

[BUGS] BUG #2358: Vacuum & \dt problems

2006-03-26 Thread Alexis Wilke
The following bug has been logged online: Bug reference: 2358 Logged by: Alexis Wilke Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: Linux 2.4.20-8 i686 Description:Vacuum & \dt problems Details: I have a database which is fairly small

Re: [BUGS] Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]

2006-03-26 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> Allowing SIGPIPE to kill the backend is completely infeasible, as the >> backend would be unable to release locks etc before dying. > So the upshot is really not that ignoring SIGPIPE is specifically > intended as the optimal solut