Re: patch for BETWEEN [ASYMMETRIC|SYMMETRIC]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: lockhart(at)fourpalms(dot)org
Cc: "Robert B(dot) Easter" <reaster(at)comptechnews(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: patch for BETWEEN [ASYMMETRIC|SYMMETRIC]
Date: 2001-01-11 03:45:03
Message-ID: 10337.979184703@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> I *assume* that this will have trouble making it in to 7.1, and since
> keywords are likely added this may have trouble with 7.1.x (not sure
> about that; perhaps the lex-generated token values never make it into
> the database tables, but they *do* propagate into structures used deeper
> in the backend).

Since he didn't add a new parsetree node type, there wouldn't be any
database compatibility issue AFAIK. I'm pretty certain that keyword
token values never get into stored rules.

However, there is our self-imposed "no new features during beta" rule.
This looks like a relatively harmless patch, but do we want to break
that rule for something that people are not beating down our doors for?

I'd vote for holding it for 7.2, I think.

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Lincoln Yeoh 2001-01-11 07:43:39 Lock on arbitrary string feature
Previous Message Thomas Lockhart 2001-01-11 03:32:54 Re: patch for BETWEEN [ASYMMETRIC|SYMMETRIC]