Re: Why does ExecComputeStoredGenerated() form a heap tuple

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Why does ExecComputeStoredGenerated() form a heap tuple
Date: 2019-04-01 09:25:46
Message-ID: cff0f562-da0d-a3ed-9c99-e3ccadb29d65@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-03-31 05:00, Andres Freund wrote:
> Also, have you actually benchmarked this code? ISTM that adding a
> stored generated column would cause quite noticable slowdowns in the
> COPY path based on this code.

Yes, it'll be slower than not having it, but it's much faster than the
equivalent trigger.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-04-01 09:26:30 Re: C_C_A animal on HEAD gets stuck in initdb
Previous Message Peter Eisentraut 2019-04-01 09:23:47 Re: Why does ExecComputeStoredGenerated() form a heap tuple