Re: Change lock requirements for adding a trigger
From:
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:
Decibel! <decibel(at)decibel(dot)org>
Cc:
Simon Riggs <simon(at)2ndquadrant(dot)com>,
PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject:
Re: Change lock requirements for adding a trigger
Date:
2008-06-04 14:59:25
Message-ID:
24709.1212591565@sss.pgh.pa.us (view raw or flat )
Thread:
2008-05-30 00:18:31 from Decibel! <decibel(at)decibel(dot)org>
2008-05-30 14:51:34 from Simon Riggs <simon(at)2ndquadrant(dot)com>
2008-06-03 21:48:08 from Decibel! <decibel(at)decibel(dot)org>
2008-06-03 22:04:13 from Simon Riggs <simon(at)2ndquadrant(dot)com>
2008-06-04 13:31:46 from Decibel! <decibel(at)decibel(dot)org>
2008-06-04 14:59:25 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2008-06-04 20:28:08 from Simon Riggs <simon(at)2ndquadrant(dot)com>
2008-06-04 20:33:20 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2008-06-04 21:09:55 from Simon Riggs <simon(at)2ndquadrant(dot)com>
2008-06-13 20:06:50 from Simon Riggs <simon(at)2ndquadrant(dot)com>
2008-07-17 01:34:29 from Bruce Momjian <bruce(at)momjian(dot)us>
Lists:
pgsql-hackers
Decibel! <decibel(at)decibel(dot)org> writes:
> Ok, I'll take a stab at such a list. Can anyone think of any reasons
> why CREATE TRIGGER couldn't get by with ShareLock?
pg_class.reltriggers.
regards, tom lane
In response to
Responses
pgsql-hackers by date
Next :From: Andreas PflugDate: 2008-06-04 15:10:37
Subject : Re: Overhauling GUCS
Previous :From : Tom LaneDate : 2008-06-04 14:56:44
Subject : Re: Proposal: new function array_init