Re: open and close columns in the NEW record not allowed

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>
Cc: Rafael Martinez Guerrero <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, zahid(dot)iqbal(at)enterprisedb(dot)com
Subject: Re: open and close columns in the NEW record not allowed
Date: 2014-02-07 16:58:28
Message-ID: CA+TgmoaEA_eYzDTUeM+oSw5wRtKkswoQ4OT3=PCPUunJCV=hKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 6, 2014 at 10:27 AM, ktm(at)rice(dot)edu <ktm(at)rice(dot)edu> wrote:
>> Thanks for the feedback.
>>
>> Our problem is that an application decides the name of the columns in
>> the tables and "XDB replication" from EnterpriseDB decides the triggers.
>> We have no control over the code :-(
>>
>
> It sounds like a bug in the XDB trigger generation code. Maybe file a bug
> report.

+1. If you are using XDB, presumably that means you are an
EntepriseDB customer and can file a support ticket. Zahid's team is
usually very responsive, and this definitely sounds like a bug.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-02-07 19:35:35 Re: Changeset Extraction v7.5
Previous Message Tom Lane 2014-02-07 15:21:16 Re: Inconsistency between pg_stat_activity and log_duration