Re: Hints (was Poor performance using CTE) - Mailing list pgsql-performance

From Tom Lane
Subject Re: Hints (was Poor performance using CTE)
Date
Msg-id 6609.1353519586@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hints (was Poor performance using CTE)  (Craig James <cjames@emolecules.com>)
List pgsql-performance
Craig James <cjames@emolecules.com> writes:
> On Wed, Nov 21, 2012 at 9:25 AM, Joe Conway <mail@joeconway.com> wrote:
>> I like this idea, but also think that if we have a syntax to allow
>> hints, it would be nice to have a simple way to ignore all hints (yes, I
>> suppose I'm suggesting yet another GUC). That way after sprinkling your
>> SQL with hints, you could easily periodically (e.g. after a Postgres
>> upgrade) test what would happen if the hints were removed.

> Or a three-way choice: Allow, ignore, or generate an error.  That would
> allow developers to identify where hints are being used.

Throwing errors would likely prevent you from reaching all parts of your
application, thus preventing complete testing.  Much more sensible to
just log such queries.

            regards, tom lane


pgsql-performance by date:

Previous
From: Joe Conway
Date:
Subject: Re: Hints (was Poor performance using CTE)
Next
From: Andreas Kretschmer
Date:
Subject: Re: Hints (was Poor performance using CTE)