Re: Partitioning feature ... - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Partitioning feature ...
Date
Msg-id 49D23DF1.5000809@dunslane.net
Whole thread Raw
In response to Re: Partitioning feature ...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Partitioning feature ...  (Nikhil Sontakke <nikhil.sontakke@enterprisedb.com>)
List pgsql-hackers

Tom Lane wrote:
>> We already have system triggers -- the FK triggers.  I don't think we've
>> had all that much trouble with them.
>>     
>
> In the case of the FK triggers, it's intentional (and maybe even
> documented) that users should be able to place their own triggers before
> or after the FK triggers. 

If it's documented I think it's well hidden ;-) ISTM that the fact that 
we implement FK constraints via triggers is really an implementation 
detail, not something the user should be encouraged to mess with.

>  Is there a good reason why partitioning
> triggers should be different?  
>   

Probably not. ISTM that the scheme should turn tgisconstraint into a 
multi-valued item (tgkind: 'u' = userland, 'c'= constraint, 'p' = 
partition or some such).

cheers

andrew






pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: [GENERAL] string_to_array with empty input
Next
From: Greg Stark
Date:
Subject: Re: string_to_array with empty input