| From: | Jayson Hreczuck <jayson(dot)hreczuck(at)studentuniverse(dot)com> |
|---|---|
| To: | Mai Peng <maily(dot)peng(at)webedia-group(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Deploy modifications of database objects |
| Date: | 2021-06-22 13:28:33 |
| Message-ID: | CAHg7=h7ySATZMMqGgX4Y+JnkAFSB4PDRRzj5PWdP0WtQ=LKN0Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
You could use different schemas, but that seems like overkill to me.
What I would do, is make sure the function code is backwards compatible,
and just replace. Or alternatively, you could have a master function run
child functions depending on what version you need.
On Tue, Jun 22, 2021 at 9:00 AM Mai Peng <maily(dot)peng(at)webedia-group(dot)com>
wrote:
> Hello everyone,
>
> We often deploy modified function code to production database. In order to
> impact the less users that still use the old version of these functions, we
> add another function. I think it’s not relevant.
> How could we deploy these modifications ? Add a schema per version ?
> Thank you in advance.
> Mai
>
>
--
*Jayson Hreczuck | Principal Database AdministratorC: +1 617.571.9861*130
Turner St, Ste 530, Waltham, MA 02453
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Smith | 2021-06-22 15:31:33 | Re: Deploy modifications of database objects |
| Previous Message | Mai Peng | 2021-06-22 13:00:28 | Deploy modifications of database objects |