Re: libpq CREATE DATABASE operation from multiple treads
От | p.sun.fun@gmail.com |
---|---|
Тема | Re: libpq CREATE DATABASE operation from multiple treads |
Дата | |
Msg-id | 9109e992e899b2ed39b070cd12ecdbcdf435fbb6.camel@gmail.com обсуждение исходный текст |
Ответ на | Re: libpq CREATE DATABASE operation from multiple treads (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: libpq CREATE DATABASE operation from multiple treads
|
Список | pgsql-sql |
On Thu, 2020-10-08 at 16:56 -0400, Tom Lane wrote: > Rob Sargent <robjsargent@gmail.com> writes: > > OK, well that’s a special db. Didn’t know it was that special, > > though! > > It's not that special. The issue here is that each session is > connecting > to template1 and then trying to clone template1. You can't clone an > active database, because you might not get a consistent copy. CREATE > DATABASE knows that its own session isn't concurrently making any > changes, so it allows copying the current database --- but it can't > know what some other session is doing, so if it sees some other > session > is also connected to the source database, it spits up. > > As I already said, routinely connecting to template1 is pretty bad > practice to start with, so the preferred answer is "don't do that". > > regards, tom lane Thank you, guys. I will switch to the "postgres" database as a default one. IMHO, it is worth adding to the documentation into the CREATE DATABASE section. I am glad that PostgreSQL has a strong community that stays behind the product.
В списке pgsql-sql по дате отправления: