Hi,
I'm in a situation where I urgently need to debug PostgreSQL 7.0.2
for deadlocks that it does not notice/timeout
Where can I find info about running several concurrent backends
under a debugger ?
---
Hannu
I just wanted to repost this one more time in case developers didn't
catch it. I have a reliable way to make postgresql crash after a
couple of hours over here and a backtrace that looks like a good
catch.
My apologies if this one time to many, I won't be posting it again.
thanks for your
On Mon, Oct 02, 2000 at 12:00:46PM -0400, Bruce Momjian wrote:
I have committed this patch. It offers a speed up to ecpg.
Thanks. I haven't found the time to do it so far. But since I wanted to this
is good news. :-)
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use
Hello all,
Please help me with
create function days_in_month(int4, int4, int4) returns int4
as '/tmp/days.so' language 'c';
Can I write this function days_in_month in C++ ?
I've did the following:
extern "C" {
int days_in_month(int year, int mo, int day);
}
extern "C" {
int
Stephan Szabo wrote:
On Sun, 1 Oct 2000, Peter Eisentraut wrote:
Stephan Szabo writes:
With that, I do have a general question though. Are referential actions
supposed to be limited by the permissions of the user executing the query?
So, if you for example have write access on the
Hannu Krosing [EMAIL PROTECTED] writes:
I'm in a situation where I urgently need to debug PostgreSQL 7.0.2
for deadlocks that it does not notice/timeout
The most likely bet is that you are seeing deadlocks that involve a
buffer spinlock (LockBuffer() in bufmgr.c) --- there's no timeout or
Hello all,
I thought I would give it a try anyways...
This data type is based on Garrett A. Wollman isbn / issn code
It can be downloaded from:
ftp://ftp.freaky-namuh.com/pub/devel/Postgresql/version_number/version_number-0.2.tar.gz
The README file explains most of it.
It's not perfect, but
A client just got this error. Anyone know why I suddenly get this?
The program has been working flawlessly for months before this.
WaitOnLock: error on wakeup - Aborting this transaction
--
D'Arcy J.M. Cain darcy@{druid|vex}.net | Democracy is three wolves
http://www.druid.net/darcy/
Michael Meskes [EMAIL PROTECTED] writes:
Anyway, the problem is that some rules expand to either Iconst, FCONST or
Sconst. So do I have to change all these rules?
Just changing the rule for Iconst and Sconst e.g doesn't work since
AexprConst expands to the variable in two different ways.
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
WaitOnLock: error on wakeup - Aborting this transaction
What happens to NOTICEs in your application?
For some odd reason, deadlock reports come out as a NOTICE followed by
this error message; if you are bit-bucketing NOTICEs then you may well
be
Fabrice Scemama [EMAIL PROTECTED] writes:
By the way, we finally understood that our main problem,
the one that was making our Pg hang forever, comes from
a deadlock problem. Same as Hannu's one.
There are no deadlock detection, indeed. Good DBAs, or
DBAs working with good coders, will
Just a little question :
When I drop a database "xxx", and create another with the same name
"xxx", old database sequences are always.
Why ?
Olivier
On Wed, 4 Oct 2000, Jan Wieck wrote:
Stephan Szabo wrote:
On Sun, 1 Oct 2000, Peter Eisentraut wrote:
Stephan Szabo writes:
With that, I do have a general question though. Are referential actions
supposed to be limited by the permissions of the user executing the query?
I have a problem with inheritance and references.
TABLE parent_table (
id_parent SERIAL PRIMARY KEY,
)
No primary key in child
TABLE child_parent (
.
) INHERITS (parent_table);
And another table :
TABLE other_table (
ref_child_table INTEGER REFERENCES parent_table
);
Reference must
Greetings,
Well, it seems that the numeric issue I was having has nothing to do with
the precision and scale being set the same, it has to do with the input
data. The precision has to be at least 2 greater than the biggest number
you need to enter, i.e.
equinox=# create table test ( d
Matthew Hagerty [EMAIL PROTECTED] writes:
Well, it seems that the numeric issue I was having has nothing to do with
the precision and scale being set the same, it has to do with the input
data. The precision has to be at least 2 greater than the biggest number
you need to enter, i.e.
16 matches
Mail list logo