Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Bryn Llewellyn <bryn(at)yugabyte(dot)com>
Cc: pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
Date: 2023-03-08 01:03:14
Message-ID: CAKFQuwaihWfF9U1LvZMg3DQiXS55Rk2KA-HH1bUVPstpsdza1Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Mar 7, 2023 at 5:52 PM Bryn Llewellyn <bryn(at)yugabyte(dot)com> wrote:

>
> Regard a DDL on any object that an application uses as unsafe while the
> app is in use. You must terminate all client-sessions before doing such a
> DDL and re-start them only when all such DDLs are done successfully.
>
>
No. If you simply "ADD COLUMN" to an existing table the "terminate all
client-sessions" action is excessive, IMO.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Siddharth Jain 2023-03-08 01:28:13 could not bind IPv4 address "127.0.0.1": Address already in use
Previous Message Bryn Llewellyn 2023-03-08 00:52:39 Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses