public inbox for [email protected]
help / color / mirror / Atom feedDDL in active production database
3+ messages / 3 participants
[nested] [flat]
* DDL in active production database
@ 2023-09-25 00:01 Skelton, Adam J <[email protected]>
2023-09-25 00:06 ` Re: DDL in active production database David G. Johnston <[email protected]>
2023-09-25 09:58 ` Sv: DDL in active production database Andreas Joseph Krogh <[email protected]>
0 siblings, 2 replies; 3+ messages in thread
From: Skelton, Adam J @ 2023-09-25 00:01 UTC (permalink / raw)
To: [email protected] <[email protected]>
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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: DDL in active production database
2023-09-25 00:01 DDL in active production database Skelton, Adam J <[email protected]>
@ 2023-09-25 00:06 ` David G. Johnston <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: David G. Johnston @ 2023-09-25 00:06 UTC (permalink / raw)
To: Skelton, Adam J <[email protected]>; +Cc: [email protected] <[email protected]>
On Sunday, September 24, 2023, Skelton, Adam J <[email protected]>
wrote:
>
> Does Postgres have problems with creation / changes to database schema
> objects when the database is actively being used?
>
It doesn’t have problems. It does require locks that can preclude active
use of those table for selects and updates while the DDL is processing.
Whether that is an issue for your application depends on the application.
And the duration required depending upon table size and the specific
command.
David J.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Sv: DDL in active production database
2023-09-25 00:01 DDL in active production database Skelton, Adam J <[email protected]>
@ 2023-09-25 09:58 ` Andreas Joseph Krogh <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Andreas Joseph Krogh @ 2023-09-25 09:58 UTC (permalink / raw)
To: Skelton, Adam J <[email protected]>; +Cc: [email protected] <[email protected]>
På mandag 25. september 2023 kl. 02:01:28, skrev Skelton, Adam J <
[email protected] <mailto:[email protected]>>:
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.
It will cause problems if you mix DDL and DML when having deferred constraints
with following updates in the same TX.
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
[email protected] <mailto:[email protected]>
www.visena.com <https://www.visena.com;
<https://www.visena.com;
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2023-09-25 09:58 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-09-25 00:01 DDL in active production database Skelton, Adam J <[email protected]>
2023-09-25 00:06 ` David G. Johnston <[email protected]>
2023-09-25 09:58 ` Sv: DDL in active production database Andreas Joseph Krogh <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox