Re: 'Weird' errors

From: Martin Gainty <mgainty(at)hotmail(dot)com>
To: <dev(at)archonet(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: 'Weird' errors
Date: 2009-09-17 19:29:24
Message-ID: BLU142-W1366FC00C7184264F09518AEE10@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


thanks for the prompt response
i took the stack of bad calls and placed them in a .sh and they all ran flawlessly..
there is a delta in there somewhere

I have a followup (if i may)
I am able to get past the initdb but when i run the postgres on the data folder I get no postgresql.conf found specifically
postgres cannot access the server configuration file "/cygdrive/c/Postgres/pgsql/data/postgresql.conf'

is there a foolproof way that I will allow postgres to access postgresql.conf?

thanks!
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.

> Date: Thu, 17 Sep 2009 19:35:30 +0100
> From: dev(at)archonet(dot)com
> To: mgainty(at)hotmail(dot)com
> CC: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] 'Weird' errors
>
> Martin Gainty wrote:
> > experiencing weird 14001 errors .no logs not evt nothing to go by so i completely rebuilt the cygwin postgres
> >
> > ran cygwin
> > then i ran the initdb as follows
> >
> > $ ./postgresql-8.4.1/src/bin/initdb/initdb.exe -D /pgsql/data
> > The files belonging to this database system will be owned by user "postgres".
> > This user must also own the server process.
> >
> > The database cluster will be initialized with locale C.
> > The default database encoding has accordingly been set to SQL_ASCII.
> > The default text search configuration will be set to "english".
> >
> > creating directory /pgsql/data ... ok
> > creating subdirectories ... ok
> > selecting default max_connections ... sh: line 1: 2752 Bad system call
> > "/cygdrive/c/Postgres/postgresql-8.4.1/src/bin/initdb/postgres.exe" --boot -x0 -
> > F -c max_connections=100 -c shared_buffers=1000 < "/dev/null" > "/dev/null" 2>&1
>
> Googling "cygwin bad system call" gets me this:
> http://people.maths.ox.ac.uk/~nichol/cruftscraper/cygwinenv.shtml
>
> The CYGWIN environment variable
> ...
> (no)server - if set, allows client applications to use the Cygserver
> facilities. This option must be enabled explicitely on the client side,
> otherwise your applications won't be able to use the XSI IPC function
> calls (msgget, semget, shmget, and friends) successfully. These function
> calls will return with ENOSYS, "Bad system call".
>
> Looks like this environment setting differs in the two environments.
>
> --
> Richard Huxton
> Archonet Ltd
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
http://clk.atdmt.com/GBL/go/171222985/direct/01/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bill Moran 2009-09-17 19:31:12 Re: limiting query time and/or RAM
Previous Message Scott Marlowe 2009-09-17 19:23:02 Re: limiting query time and/or RAM