Re: [HACKERS] pg_class.relpartbound definition overly brittle - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] pg_class.relpartbound definition overly brittle
Date
Msg-id 14809.1496323879@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] pg_class.relpartbound definition overly brittle  (Mark Dilger <hornschnorter@gmail.com>)
Responses Re: [HACKERS] pg_class.relpartbound definition overly brittle  (Mark Dilger <hornschnorter@gmail.com>)
Re: [HACKERS] pg_class.relpartbound definition overly brittle  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Mark Dilger <hornschnorter@gmail.com> writes:
> When you guys commit changes that impact partitioning, I notice, and change
> my code to match.  But in this case, it seemed to me the change that got
> committed was not thought through, and it might benefit the community for
> me to point it out, rather than quietly make my code behave the same as
> what got committed.

Let me explain the project standards in words of one syllable: user code
should not examine the contents of node trees.  That's what pg_get_expr
is for.  There is not, never has been, and never will be any guarantee
that we won't whack those structures around in completely arbitrary ways,
as long as we do a catversion bump along with it.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: retry shm attach for windows (WAS: Re: [HACKERS] OK, so culicidae is *still* broken)
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] tap tests on older branches fail if concurrency is used