î<¡§ˆ¿e?'¿JÈ7vÛ£Š1YÇ2G»ÖQʺ|6¡
”:dJ<‚ÚDØGèÎÉÉ¿“¤osoò!2^%Á&UʹģàïeûÄû×zGë5êlñ|Õ6ch9Úæ‰E"ýÁ¼754«³Ôä?Vü°G¼$Ó2ÇöíeJ
n¿ËqéÖÈ‹cúÀyw//žÉqΈAä4ò¬•Â"çqKFÕÐ#"n¸»IDÏ&
ÕL½7_úõç>4ãÓûá4c~a¢Ù‚vú—JÜšÝy±òRHmyÐw‡
B\cÝÒÍ]V‚ˆ,9°†6_‘|ScGéX‡Â¹1Æx™JݬàVS4J¡2¥ôNô#Íi<"ôtDȺšIkb«¤?¬½NR·9©éMu¥Ÿa}„}lBÖ»3u„9¼Qu·?ê#£\Ö”í²°?
Kris Jurka <[EMAIL PROTECTED]> writes:
> 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 unre
On Mon, 2 Feb 2004, Hamedany, Allen wrote:
> 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 co
> /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
>
>
>
>
>
>
>
> +=
