From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: optimizer/clauses.h needn't include access/htup.h
Date: Mon, 23 Nov 2020 19:44:37 -0300
Message-ID: <20201123224437.GA1593@alvherre.pgsql> (raw)
In-Reply-To: <166715.1606168841@sss.pgh.pa.us>
On 2020-Nov-23, Tom Lane wrote:
> Anyway, if you're feeling motivated to explore a more wide-ranging
> refactoring, by all means have a go at it.
I was contemplating commands/trigger.c this morning (after Heikki split
copy.c) thinking about the three pieces embedded in there -- one
catalog/pg_trigger.c, one in executor (execTrigger.c?) and what seems a
very small piece to remain where it is.
Just thinking out loud ...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, pryzby@telsasoft.com, pgsql-hackers@lists.postgresql.org
Subject: Re: optimizer/clauses.h needn't include access/htup.h
In-Reply-To: <20201123224437.GA1593@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox