Re: Controlling changes in plpgsql variable resolution - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Controlling changes in plpgsql variable resolution
Date
Msg-id 9876.1255896470@sss.pgh.pa.us
Whole thread Raw
In response to Re: Controlling changes in plpgsql variable resolution  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Controlling changes in plpgsql variable resolution
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> If possible, I think we should try to engineer things so that using
> pg_dump 8.5 on an 8.4 database and restoring the result into an 8.5
> database produces a function with identical semantics.

Hmm ... actually, we could have pg_dump stick either a #option line
or a GUC SET parameter onto every plpgsql function it pulls from an
old database.  So if you're willing to assume that people do their
upgrades that way, it could be made reasonably safe, even if the
default behavior changes.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: LATERAL
Next
From: Tom Lane
Date:
Subject: Re: Boosting cost estimates for some built-in functions