DDL in active production database

From: "Skelton, Adam J" <Adam(dot)Skelton(at)fisglobal(dot)com>
To: "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org>
Subject: DDL in active production database
Date: 2023-09-25 00:01:28
Message-ID: VE1PR08MB559746D4BEA543C96A8DB57F81FCA@VE1PR08MB5597.eurprd08.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Hi,

I hope I have the correct group here.

I have a question that I am struggling to find answers for in the documentation. Does Postgres have problems with creation / changes to database schema objects when the database is actively being used?

In particular - rightly or wrongly - our developers want our application to occasionally issue the following kinds of DDL when it's in active use

Alter table ... add column ...
Create / drop materialised view ...
Create / drop table created with INHERITANCE

I know oracle hates this and you can run into some serious issues, SQL server generally lets you away with it.

Should we expect problems if we decided to do this in the latest version of Postgres?

Thanks for your time.
Adam
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message David G. Johnston 2023-09-25 00:06:19 Re: DDL in active production database
Previous Message Jean-Marc Voillequin (MA) 2023-09-18 14:05:24 RE: no_data_found oracle vs pg