Re: allow trigger to get updated columns

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: allow trigger to get updated columns
Date: 2020-03-09 08:39:31
Message-ID: 4e534c8d-4c04-6a30-e8e9-aecdec917ccc@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-03-05 13:53, Daniel Gustafsson wrote:
> The 0001 refactoring patch seems a clear win to me.
>
> In the 0002 patch:
>
> + For <literal>UPDATE</literal> triggers, a bitmap set indicating the
> + columns that were updated by the triggering command. Generic trigger
>
> Is it worth pointing out that tg_updatedcols will be NULL rather than an empty
> Bitmapset for non-UPDATE triggers? bitmapset.c treats NULL as an empty bitmap
> but since a Bitmapset can be allocated but empty, maybe it's worth being
> explicit to help developers?

done

> There isn't really a test suite that excercises this IIUC, how about adding
> something like the attached diff to contrib/lo? It seemed like a lower impact
> change than widening test_tsvector.

done

> +1 on the patchset, marking this entry as Ready For Committer.

and done

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2020-03-09 08:39:59 Re: Add an optional timeout clause to isolationtester step.
Previous Message Masahiko Sawada 2020-03-09 08:38:31 Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager