From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Thalis Kalfigkopoulos <tkalfigo(at)gmail(dot)com> |
Cc: | Igor Neyman <ineyman(at)perceptron(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Drop/Re-Creating database extremely slow + doesn't lose data |
Date: | 2016-05-31 14:19:58 |
Message-ID: | CAKFQuwZWFvJe6Y7C0kU1faF0FzLv=gU_EbcvabiLrrbtyz4w4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, May 31, 2016 at 10:06 AM, Thalis Kalfigkopoulos <tkalfigo(at)gmail(dot)com>
wrote:
> @DavidJohnston, I don't know why, but yes, I am doing all operations
> connected from template1.
>
>>
>> Oddly, the notes on the aforementioned page state: "The principal
>> limitation is that no other sessions can be connected to the template
>> database while it is being copied." yet in your example you appear to be
>> connected to template1 when you execute the CREATE DATABASE command...
>>
>>
The convention on these lists is to bottom-post (or inline). Top-posting
is greatly disliked as it makes it difficult for observers to follow and
catch-up on an existing thread.
As to my observation - I failed to process the word "other"; the issuing
session can be connected to the template but that is all. This is OK
because the current session would be unable to affect any other changes
while the CREATE DATABASE is in progress.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-05-31 14:20:22 | Re: Switching roles as an replacement of connection pooling tools |
Previous Message | Achilleas Mantzios | 2016-05-31 14:18:40 | Re: Switching roles as an replacement of connection pooling tools |