Hi,
In your example, it seems that process B is the first such waiter( the
request of B conflicts AccessShareLock).
Best regards.
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "ipig" <[EMAIL PROTECTED]>
Cc: "Bruce Momjian
head, since
the first waiter in the queue must conflict with the lock-held process.
Best wishes.
- Original Message -
From: "Bruce Momjian"
To: "ipig" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, May 29, 2006 11:26 PM
Subject: Re: [HACKERS] some question about dead
-
From: "Bruce Momjian"
To: "ipig" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, May 29, 2006 9:49 PM
Subject: Re: [HACKERS] some question about deadlock
> ipig wrote:
>> Hi,
>>
>> Below is the notes from postgresql-8.1.3/src/backend/storage/lmgr/README:
>&g
Hi,
Below is the
notes from postgresql-8.1.3/src/backend/storage/lmgr/README:
Lock acquisition (routines LockAcquire and ProcSleep) follows
these rules:
1. A lock request is granted immediately if it does not
conflict withany existing or waiting lock request, or if the pr
Hi,
I am now studying PostgreSQL.
in your web site:
Developer's Frequently Asked Questions (FAQ) for
PostgreSQL
Technical Questions
2.1) How do I efficiently access information in
tables from the backend code?
Since heap_open function needs the oid of the
relation, h
As Qingqing Zhou said, i misread "exist".
Thanks.
- Original Message -
From: "Gurjeet Singh" <[EMAIL PROTECTED]>
To: "ipig" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, May 16, 2006 11:36 AM
Subject: Re: [HACKERS] Why use " != "
Hi,
in postgresql-8.1.3/src/backend/storage/lmgr/proc.c
there are 2 function InitProcess and
InitDummyProcess, both use
" if (MyProc != NULL) elog(ERROR,
"you already exist"); " (line 215 and 315)
why use " != " ?
Best regards.
Maybe you can develop a graphic interface just like Fedora Core setup interface
which can choose packages installing, then the user can choose config file and
then have a little change in parameters.
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Jonah H. Harris" <[EMAI
