| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gary Stainburn <gary(dot)stainburn(at)ringways(dot)co(dot)uk> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: createdb problem |
| Date: | 2003-10-14 17:38:33 |
| Message-ID: | 11050.1066153113@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Gary Stainburn <gary(dot)stainburn(at)ringways(dot)co(dot)uk> writes:
> Am I right in thinking that dropdb actually connects using the template1
> database to enable it to work, and that the connection is not closing quick
> enough when dropdb finishes, thus causing the problem?
Yes. I'd suggest issuing the DROP and CREATE commands in the same psql
session, instead of relying on dropdb's backend to terminate before
createdb's has run. Because the backends are background processes in
the eyes of the kernel, they can easily not get scheduled when there is
anything else to do.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Browne | 2003-10-14 19:00:11 | Re: Lock! |
| Previous Message | Andrew Sullivan | 2003-10-14 16:51:34 | Re: Security Problem |