| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] generated columns |
| Date: | 2017-12-27 17:31:05 |
| Message-ID: | 1bc948f8-3bab-6c54-50af-c0723a75b85f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/12/17 15:35, Jaime Casanova wrote:
> On 10 September 2017 at 00:08, Jaime Casanova
> <jaime(dot)casanova(at)2ndquadrant(dot)com> wrote:
>>
>> During my own tests, though, i found some problems:
Here is an updated patch that should address the problems you have found.
> also is interesting that in triggers, both before and after, the
> column has a null. that seems reasonable in a before trigger but not
> in an after trigger
Logically, you are correct. But it seems excessive to compute all
virtual columns for every trigger. I don't know how to consolidate
that, especially with the current trigger API that lets
you look more or less directly into the tuple.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Generated-columns.patch | text/plain | 106.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antonio Belloni | 2017-12-27 17:40:43 | Contributing some code |
| Previous Message | Jeremy Finzel | 2017-12-27 16:50:19 | Re: Deadlock in multiple CIC. |