Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> I'll see if I can repro a case like it to see if the syslogger prevents
>> the shared mem from going away when I get back to a dev box. Should be
>> enough to just stick a sleep preventing it from stopping, right?
>
> The syslogger i
Roberts, Jon wrote:
>> Roberts, Jon wrote:
Not having looked at the internals of db_link, I'd say it's
> certainly
possible that this is the reason for the failed restart. If db_link
> is
blocking something, the postmaster can't kill it off, and it'll
> still
>>> be
sitting ther
> Roberts, Jon wrote:
> >> Not having looked at the internals of db_link, I'd say it's
certainly
> >> possible that this is the reason for the failed restart. If db_link
is
> >> blocking something, the postmaster can't kill it off, and it'll
still
> > be
> >> sitting there holding a reference to th
Magnus Hagander <[EMAIL PROTECTED]> writes:
> I'll see if I can repro a case like it to see if the syslogger prevents
> the shared mem from going away when I get back to a dev box. Should be
> enough to just stick a sleep preventing it from stopping, right?
The syslogger isn't restarted at all dur
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Not likely, but I'd test it anyway. If the issue is related to AV, it's
>> certainly fine - you won't be running AV on your Solaris. But more
>> importantly, Unix has actual support for signals and not just the fake
>> stuff we have o
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Not likely, but I'd test it anyway. If the issue is related to AV, it's
> certainly fine - you won't be running AV on your Solaris. But more
> importantly, Unix has actual support for signals and not just the fake
> stuff we have on Win32, so it's likel
BTW, just looking at win32_shmem.c ...
retptr = malloc(bufsize + 1 + 18);/* 1 NULL and 18 for
* Global\PostgreSQL: */
if (retptr == NULL)
elog(FATAL, "could not allocate memory for shared memory name");
strcpy(retptr, "Global\\Pos
"Roberts, Jon" <[EMAIL PROTECTED]> writes:
> I'm not complaining. I just want to make sure that if I upgrade, it
> will fix the problem. An upgrade could possible introduce a new
> problem. I also wonder if this is isolated to Win32 because we are
> upgrading to Solaris very soon.
The specific
Roberts, Jon wrote:
>> Not having looked at the internals of db_link, I'd say it's certainly
>> possible that this is the reason for the failed restart. If db_link is
>> blocking something, the postmaster can't kill it off, and it'll still
> be
>> sitting there holding a reference to the shared mem
>
> Not having looked at the internals of db_link, I'd say it's certainly
> possible that this is the reason for the failed restart. If db_link is
> blocking something, the postmaster can't kill it off, and it'll still
be
> sitting there holding a reference to the shared memory segment.
>
> That
Roberts, Jon wrote:
>> Roberts, Jon wrote:
Tom Lane wrote:
> "Roberts, Jon" <[EMAIL PROTECTED]> writes:
>> Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
> Well, there are plenty of known bugs in 8.3.0 by now. You really
> should update before complaining, not
> Roberts, Jon wrote:
> >> Tom Lane wrote:
> >>> "Roberts, Jon" <[EMAIL PROTECTED]> writes:
> Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
> >>> Well, there are plenty of known bugs in 8.3.0 by now. You really
> >>> should update before complaining, not after.
> >> Yes. And
Roberts, Jon wrote:
>> Tom Lane wrote:
>>> "Roberts, Jon" <[EMAIL PROTECTED]> writes:
Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
>>> Well, there are plenty of known bugs in 8.3.0 by now. You really
>>> should update before complaining, not after.
>> Yes. And the traditiona
Roberts, Jon wrote:
"Roberts, Jon" <[EMAIL PROTECTED]> writes:
Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.
I'm not complaining. I just want to make sure that if I
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> But the syslogger process (and maybe others) is *not* supposed to
die.
>
> > Right. But are you saying we actually want to start up a new backend
in
> > a directory where we already have a running syslogger (and maybe
others)
>
> Tom Lane wrote:
> > "Roberts, Jon" <[EMAIL PROTECTED]> writes:
> >> Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
> >
> > Well, there are plenty of known bugs in 8.3.0 by now. You really
> > should update before complaining, not after.
>
> Yes. And the traditional question shou
> "Roberts, Jon" <[EMAIL PROTECTED]> writes:
> > Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
>
> Well, there are plenty of known bugs in 8.3.0 by now. You really
> should update before complaining, not after.
I'm not complaining. I just want to make sure that if I upgrade, it
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> But the syslogger process (and maybe others) is *not* supposed to die.
> Right. But are you saying we actually want to start up a new backend in
> a directory where we already have a running syslogger (and maybe others)
> processes,
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> Another problem is that postmaster children that do
>>> PGSharedMemoryDetach will still have valid inherited handles for
>>> the shmem segment --- does that factor into the behavior? It looks
>>> to me like the Cl
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Another problem is that postmaster children that do
>> PGSharedMemoryDetach will still have valid inherited handles for
>> the shmem segment --- does that factor into the behavior? It looks
>> to me like the CloseHandle ought to be i
Tom Lane wrote:
> "Roberts, Jon" <[EMAIL PROTECTED]> writes:
>> Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
>
> Well, there are plenty of known bugs in 8.3.0 by now. You really
> should update before complaining, not after.
Yes. And the traditional question should be asked - i
"Roberts, Jon" <[EMAIL PROTECTED]> writes:
> Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.
> Problem: My database keeps on crashing every few days with this type of
> er
22 matches
Mail list logo
