| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Subject: | Re: Command Triggers, patch v11 |
| Date: | 2012-03-13 15:14:06 |
| Message-ID: | 1331651567-sup-508@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Andres Freund's message of mar mar 13 08:22:26 -0300 2012:
> - I think list_command_triggers should do a heap_lock_tuple(LockTupleShared)
> on the command trigger tuple. But then again just about nothing else does :(
If you want to do something like that, I think it's probably more
appropriate to use LockDatabaseObject than heap_lock_tuple.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2012-03-13 15:14:33 | Re: pg_upgrade and statistics |
| Previous Message | Kevin Grittner | 2012-03-13 15:11:16 | Re: subselect in the column list |