| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>, Kedar Potdar <kedar(dot)potdar(at)gmail(dot)com>, Emmanuel Cecchet <manu(at)asterdata(dot)com>, pgsql-hackers(at)postgresql(dot)org, Amit Gupta <amit(dot)pc(dot)gupta(at)gmail(dot)com> |
| Subject: | Re: Partitioning feature ... |
| Date: | 2009-03-31 15:21:01 |
| Message-ID: | 3073cc9b0903310821m55caed54l6b2763b92fdcf8cf@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 31, 2009 at 9:46 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
>>
>> AFAICS, we do not have any category like system triggers. So yeah, it would
>> have been nice to generate triggers with names (starting with __ for
>> example) for such special triggers. But I don't think we disallow
>> user-triggers starting with underscores etc.
>
> We already have system triggers -- the FK triggers. I don't think we've
> had all that much trouble with them.
>
yeah! but we mark them with pg_trigger.tgisconstraint, but i'm not
completely convinced that we should use that same field
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-03-31 15:31:18 | Re: [GENERAL] pgstattuple triggered checkpoint failure and database outage? |
| Previous Message | Alvaro Herrera | 2009-03-31 15:17:25 | Re: Fwd: Abwesend: [GENERAL] string_to_array with empty input |