From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Ancient comment in rules.sgml
Date: Mon, 11 Feb 2019 11:30:45 -0500
Message-ID: <18812.1549902645@sss.pgh.pa.us> (raw)
In-Reply-To: <20190211.191004.219630835457494660.t-ishii@sraoss.co.jp>
References: <20190211.191004.219630835457494660.t-ishii@sraoss.co.jp>
Tatsuo Ishii <ishii@sraoss.co.jp> writes:
> There's a comment beginning with:
> <!-- What's happening with this? If it doesn't come back, remove this section. -->
> in rules.sgml around line 2437. It seems this has been there since 2003.
> Do we need to keep this?
Well, the point is that the whole para after that is commented out.
The para in question seems to have shown up in 20a071326, and
at the time it began
+<Para>
+ Another situation are cases on UPDATE where it depends on the
+ change of an attribute if an action should be performed or
+ not. In <ProductName>Postgres</ProductName> version 6.4, the
+ attribute specification for rule events is disabled (it will have
+ it's comeback latest in 6.5, maybe earlier
+ - stay tuned). So for now the only way to
+ create a rule as in the shoelace_log example is to do it with
+ a rule qualification. That results in an extra query that is
+ performed allways, even if the attribute of interest cannot
I think it's a safe bet at this point that that feature isn't ever
coming back, so I'd be good with ripping out the whole para.
regards, tom lane
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-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, ishii@sraoss.co.jp, pgsql-docs@lists.postgresql.org
Subject: Re: Ancient comment in rules.sgml
In-Reply-To: <18812.1549902645@sss.pgh.pa.us>
* 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