Re: read-only planner input - Mailing list pgsql-hackers

From Oliver Jowett
Subject Re: read-only planner input
Date
Msg-id 423A8E03.4020201@opencloud.com
Whole thread Raw
In response to Re: read-only planner input  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: read-only planner input
List pgsql-hackers
Tom Lane wrote:

> You could make a
> good case that we just ought to save query text and start from there in
> any replanning; it'd be the most compact representation, the easiest to
> copy around, and the least likely to break.

What happens if (for example) DateStyle changes between the two parses? 
(not that I'm sure what the expected behaviour is in that case anyway..)

-O


pgsql-hackers by date:

Previous
From: Michael Fuhr
Date:
Subject: "they only drink coffee at dec"
Next
From: Shachar Shemesh
Date:
Subject: Unstable timestamp binary representation?