Re: FOR EACH ROW triggers on partitioned tables - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: FOR EACH ROW triggers on partitioned tables
Date
Msg-id c847c761-dd14-9ea9-5aaa-1d3cf9606dd8@2ndquadrant.com
Whole thread Raw
In response to Re: FOR EACH ROW triggers on partitioned tables  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: FOR EACH ROW triggers on partitioned tables  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On 3/21/18 19:18, Alvaro Herrera wrote:
> Here's v8, which addresses all your comments except the doc updates.  I
> added a few more tests, too.  Thanks for the review!  I intend to commit
> this shortly, probably not before Friday to give some more time for
> others to review/comment.

Looks good, does what it needs to do.

A small fixup attached.  In particular, I renamed one trigger from "f",
which created confusing output, looking like a boolean column.

This comment in the tests I don't understand:

-- verify that the FOR UPDATE OF (columns) is propagated correctly

I don't see how this applies to the tests that follow.  Does this have
something to do with the subsequent foreign keys patch perhaps?

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

Attachment

pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: [PATCH] Verify Checksums during Basebackups
Next
From: Fujii Masao
Date:
Subject: Re: Using base backup exclusion filters to reduce data transferredwith pg_rewind