On 09/28/2011 08:54 PM, Maria L. Wilson wrote:
UPDATE dataset
SET gracount = gracount + 1
WHERE dataset.inv_id = NEW.inv_id;
That'll serialize all transactions that touch the same inv_id, so only
one may run at once. The second and subsequent ones will block waiting
for an update lock on the
Just a quick checkin on this problem. Thus far, I have managed to install
dbg and recompile postgresql with the appropriate debugging
headers/variables.
I have been following wiki that Scott sent, and attempted to trace one of my
pg processes while making it crash. I have "succeeded" in causing
Hi,
I install pg 9.0.2 on suse 11sp1,
I compile from source
Sincerely,
Kasia
From: pgsql-admin-ow...@postgresql.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of ALEXANDER JOSE
Sent: Tuesday, September 27, 2011 10:38 AM
To: postgres admin
Subject: [ADMIN] Postgres 9 on 64 bit
Hi,
I wan
Gilberto Castillo Martínez wrote:
>> CREATE OR REPLACE FUNCTION increment_dataset_granule_count()
>> RETURN NULL;
> Replace RETURN NULL for RETURN NEW
That won't matter for an AFTER trigger:
http://www.postgresql.org/docs/9.0/interactive/trigger-definition.html
says:
| The ret
El mié, 28-09-2011 a las 08:54 -0400, Maria L. Wilson escribió:
> Hi all
>
> I would like to start a dialogue and hear general feedback about the
> use of constraint triggers in postgres (8.4.5).
>
> Our overall issue is that using general triggers is causing slow
> inserts (from locking is
Hi all
I would like to start a dialogue and hear general feedback about the use
of constraint triggers in postgres (8.4.5).
Our overall issue is that using general triggers is causing slow inserts
(from locking issues) in our database. Here are some details:
A little background (jboss/
