Re: [HACKERS] Cached plans and statement generalization - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] Cached plans and statement generalization
Date
Msg-id 20170425214746.3mngxgbo7yndfgax@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] Cached plans and statement generalization  (Doug Doole <ddoole@salesforce.com>)
Responses Re: [HACKERS] Cached plans and statement generalization
Re: [HACKERS] Cached plans and statement generalization
List pgsql-hackers
On 2017-04-25 21:11:08 +0000, Doug Doole wrote:
> When I did this in DB2, I didn't use the parser - it was too expensive. I
> just tokenized the statement and used some simple rules to bypass the
> invalid cases. For example, if I saw the tokens "ORDER" and "BY" then I'd
> disallow replacement replacement until I hit the end of the current
> subquery or statement.

How did you manage plan invalidation and such?

- Andres



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [HACKERS] Separation walsender & normal backends
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Separation walsender & normal backends