A customer is facing a problem on PostgreSQL 8.3.10 on Windows where the
syslogger process dies mysteriously every few hours under load. I
haven't yet figured out why, but when postmaster tries to respawn
syslogger, it doesn't start up but dies immediately.
The reason the relaunch fails is that in
2010/4/1 Heikki Linnakangas :
> NULL_DEV is defined in c.h as "/dev/null", which doesn't work on
> windows. We have a port-specific #define DEVNULL which does work, we
> should be using that.
Wow. Looking at the code around NULL_DEV, that actually looks like a
merge mistake from the old windows br
The following bug has been logged online:
Bug reference: 5401
Logged by: Jyothi
Email address: jyothih...@gmail.com
PostgreSQL version: 8.4
Operating system: fedora12
Description:make: *** [pg_rman] Error 1
Details:
When i m trying to install pg_rman on fedora platf
On Thu, 2010-04-01 at 11:32 +, Jyothi wrote:
> Operating system: fedora12
> Description:make: *** [pg_rman] Error 1
> /usr/bin/ld: cannot find -lxml2
You will need to install libxml2-devel , I think.
--
Devrim GÜNDÜZ
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Post
Heikki Linnakangas writes:
> A customer is facing a problem on PostgreSQL 8.3.10 on Windows where the
> syslogger process dies mysteriously every few hours under load. I
> haven't yet figured out why, but when postmaster tries to respawn
> syslogger, it doesn't start up but dies immediately.
> Th
Andy Balholm wrote:
>> That's hardly an improvement if you're concerned about lack of
>> exactness.
>
> I know; I lose a couple of digits by using float8 instead of
> numeric, but it's much simpler and faster
It also has the advantage of being symmetrical with the other
operators.
> and if
On Apr 1, 2010, at 7:57 AM, Kevin Grittner wrote:
> I'm inclined to think it's better to have an explicit cast from
> money to numeric, as long as it is exact, and leave the division of
> money by money as float8. It does sort of beg the question of
> whether we should support a cast back in the o
Andy Balholm wrote:
> OK. Here is the whole thing in C
Cool! I'll take it for a spin when I get a little time.
I guess there's not much point adding that TODO item now. ;-)
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
Tom Lane wrote:
> Hmm. I agree with your proposed change, but it seems to me that there
> is still another mystery here: why does the mistaken open() argument
> lead to a crash? Per the second comment, this code is supposed to keep
> working even if the open() fails. If it fails because of that,
Heikki Linnakangas writes:
> The open() fails and returns a return code as you would expect. But the
> dup2() call crashes when passed an invalid file descriptor, I just
> tested that with a small test program on Windows.
Ah, thanks Windows :-(
> ! if (fd != -1)
> ! {
> !
Tom Lane wrote:
> Is that actually the cause of the original bug report, or is there
> another issue yet to solve?
I still don't know what caused syslogger to die in the first place, this
bug only affects its respawning. It might not be a PostgreSQL issue at
all, but we'll see.
--
Heikki Linna
11 matches
Mail list logo
