Re: [BUGS] createdb fails

#1

Quote:

/var/log/pgsqld.log -o -i

/usr/local/pgsql/bin/createdb management <-- fails here

/usr/local/pgsql/bin/createdb test <-- fails here

Any help on what's causing this behavior and how to fix is appreciated.

-Allen

+================================================= ======================
===================+

pgsqld.log:

2004-02-02 17:33:00 [1555] LOG: database system is ready

2004-02-02 17:33:01 [1557] LOG: connection received: host=[local]

2004-02-02 17:33:01 [1557] LOG: connection authorized: user=pgsql
database=template1

2004-02-02 17:33:01 [1557] LOG: query: begin; select
getdatabaseencoding(); commit

2004-02-02 17:33:01 [1557] LOG: duration: 0.035097 sec

2004-02-02 17:33:01 [1557] LOG: query: SELECT d.datname as "Name",

u.usename as "Owner",

pg_catalog.pg_encoding_to_char(d.encoding) as "Encoding"

FROM pg_catalog.pg_database d

LEFT JOIN pg_catalog.pg_user u ON d.datdba = u.usesysid

ORDER BY 1;

2004-02-02 17:33:01 [1557] LOG: duration: 0.024846 sec

2004-02-02 17:33:01 [1596] LOG: connection received: host=[local]

2004-02-02 17:33:01 [1596] LOG: connection authorized: user=pgsql
database=template1

2004-02-02 17:33:01 [1596] LOG: query: begin; select
getdatabaseencoding(); commit

2004-02-02 17:33:01 [1596] LOG: duration: 0.000521 sec

2004-02-02 17:33:01 [1596] LOG: query: SET autocommit TO 'on';CREATE
DATABASE "management"

2004-02-02 17:33:01 [1621] LOG: connection received: host=[local]

2004-02-02 17:33:01 [1621] LOG: connection authorized: user=pgsql
database=template1

2004-02-02 17:33:01 [1621] LOG: query: begin; select
getdatabaseencoding(); commit

2004-02-02 17:33:01 [1621] LOG: duration: 0.000509 sec

2004-02-02 17:33:01 [1621] LOG: query: SET autocommit TO 'on';CREATE
USER "management" CREATEDB CREATEUSER

2004-02-02 17:33:01 [1626] LOG: connection received: host=[local]

2004-02-02 17:33:01 [1626] LOG: connection authorized: user=pgsql
database=template1

2004-02-02 17:33:01 [1626] LOG: query: begin; select
getdatabaseencoding(); commit

2004-02-02 17:33:01 [1626] LOG: duration: 0.000509 sec

2004-02-02 17:33:01 [1626] LOG: query: SET autocommit TO 'on';CREATE
DATABASE "test"

2004-02-02 17:33:01 [1626] ERROR: CREATE DATABASE: source database
"template1" is being accessed by other users

2004-02-02 17:33:01 [1631] LOG: connection received: host=[local]

2004-02-02 17:33:01 [1631] LOG: connection authorized: user=pgsql
database=management

************************************************** ************************************
This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you.
************************************************** ************************************

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

#2

On Mon, 2 Feb 2004, Hamedany, Allen wrote:

Quote:

Running postgresql v7.3 on RH7.3 linux; db creation fails and is
reproducible after a fresh image install. Any subsequent rebooting seems
to work fine.

We start up Postgres, create users and db using a Java (IBM1.4.1) class.
The following commands are executed in the following order:

/usr/local/pgsql/bin/pg_ctl -w start -D /var/lib/pgsql -l
/var/log/pgsqld.log -o -i

/usr/local/pgsql/bin/createdb management <-- fails here
/usr/local/pgsql/bin/createdb test <-- fails here

2004-02-02 17:33:01 [1626] LOG: query: SET autocommit TO 'on';CREATE
DATABASE "test"

2004-02-02 17:33:01 [1626] ERROR: CREATE DATABASE: source database
"template1" is being accessed by other users

This is showing that the second createdb call is failing with the error
that there is an open connection to template1. In your case I wonder if
even though the "createdb management" client has exited allowing the code
to proceed to "createdb test" call, the backend associated with this
connection may not have completely shut down yet.

What happens if you add a sleep 5 call in between the createdb calls?

Kris Jurka

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

#3

Kris Jurka <books (AT) ejurka (DOT) com> writes:

Quote:

What happens if you add a sleep 5 call in between the createdb calls?

Even a fractional-second sleep would likely do it. I have traced
through scenarios like this in the past, and AFAICT the exiting backend
is not doing anything wrong or even using an unreasonable amount of
CPU time before it quits. It simply isn't getting scheduled to run
because for one reason or another the kernel gives time slices to the
foreground clients and the new backend first.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: [BUGS] createdb fails

mailing.database.pgsql-bugs mailing.database.pgsql-bugs

Re: [BUGS] createdb fails - 02-03-2004 , 02:25 AM

Re: [BUGS] createdb fails - 02-03-2004 , 05:50 AM

Re: [BUGS] createdb fails - 02-03-2004 , 09:17 AM