| From: | s d <daku(dot)sandor(at)gmail(dot)com> |
|---|---|
| To: | Leonardo M(dot) Ramé <l(dot)rame(at)griensu(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Update foreign table with trigger |
| Date: | 2016-02-26 20:11:44 |
| Message-ID: | CAKyoTgaZDEps72dhc9b1yJJi8cyTOcaCcnrC=uz23w7dosXN-A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 26 February 2016 at 21:02, Leonardo M. Ramé <l(dot)rame(at)griensu(dot)com> wrote:
>
>
> El 26/02/16 a las 16:49, s d escribió:
>
>> On 26 February 2016 at 20:42, Leonardo M. Ramé <l(dot)rame(at)griensu(dot)com
>> <mailto:l(dot)rame(at)griensu(dot)com>> wrote:
>>
>>
>>
>>
>> Then try to do the update on the remote db directly.
>>
>> In the meantime could you provide the table and trigger
>> definitions?
>>
>>
>> I don't understand why the trigger is run in the caller database
>> instead of the called (foreign) one.
>>
>>
>> It isn't. You get this error message because the reason why the local
>> command fails is in the remote trigger somewhere.
>>
>>
> But, when I update TABLE_A from the remote server everything works ok.
>
I'm pretty sure we won't get further without seeing your defs.
Ezt az e-mailt egy Avast védelemmel rendelkező, vírusmentes számítógépről
küldték.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leonardo M. Ramé | 2016-02-26 20:24:12 | Re: Update foreign table with trigger |
| Previous Message | Leonardo M. Ramé | 2016-02-26 20:02:29 | Re: Update foreign table with trigger |