Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Ok, I think I know what's happening. In btbulkdelete we have a
> PG_TRY-CATCH block. In the try-block, we call _bt_start_vacuum which
> acquires and releases the BtreeVacuumLock. Under certain error
> conditions, _bt_start_vacuum calls elog(ERROR)
"zaky" <[EMAIL PROTECTED]> writes:
> Operating System : Red Hat Release 9 (Kernel 2.4.20-8)
It's unlikely that RPMs built for current Red Hat releases would work
on such an old release. You could try getting the SRPM and rebuilding
it locally. But really better advice is "it's time for an OS up
Hi Tom, hi Mark,
Tom, thank you for having a look into this!
Tom Lane [2007-03-29 13:49 -0400]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > https://launchpad.net/bugs/93042 has symbolic gdb backtraces of all
> > three processes that are involved.
>
> Are these really all the processes involved
POSTGRESQL BUG REPORT
Name : Ahmad Zaky
Email address : [EMAIL PROTECTED]
System Configuration:
-
Architecture : Intel Pentium
Operating System : Red Hat Release 9 (Kernel
I wrote:
> It's possible that this is not a deadlock per se, but the aftermath of
> someone having errored out without releasing the BtreeVacuumLock --- but
> I don't entirely see how that could happen either, at least not without
> a core dump scenario.
On closer inspection, the autovac stack tra
Martin Pitt <[EMAIL PROTECTED]> writes:
> https://launchpad.net/bugs/93042 has symbolic gdb backtraces of all
> three processes that are involved.
Are these really all the processes involved? The createdb process and
the autovac process are both waiting for someone else to give up the
BtreeVacuum
Martin Pitt wrote:
Since our Launchpad developers switched from 8.1 to 8.2.3, they often
encounter a situation when the postmaster gets stuck and needs to be
restarted. This happens on various CREATE commands (FUNCTION,
DATABASE, not consistently).
The backtraces show that the process doing the
Martin Pitt wrote:
Since our Launchpad developers switched from 8.1 to 8.2.3, they often
encounter a situation when the postmaster gets stuck and needs to be
restarted. This happens on various CREATE commands (FUNCTION,
DATABASE, not consistently).
The backtraces show that the process doing the
Hi,
Since our Launchpad developers switched from 8.1 to 8.2.3, they often
encounter a situation when the postmaster gets stuck and needs to be
restarted. This happens on various CREATE commands (FUNCTION,
DATABASE, not consistently).
The backtraces show that the process doing the CREATION, anothe
