Thread: Re: psql 7.2 AND 7.1.3 failing on Cygwin 1.3.9 pgsql 7.2

Re: psql 7.2 AND 7.1.3 failing on Cygwin 1.3.9 pgsql 7.2

From
"Henshall, Stuart - WCP"
Date:
createlang, createdb and createuser (as well as the drops) are scripts
that invoke psql, so if psql doesn't work they wont.
Are you sure you where invoking 7.1.3's psql and not 7.2's as I've not
seen this myself (mind you I've hardly exhaustively tested).
Either way the problem that was causing psql 7.2 to fail for me has been
fixed in the last DLL snapshot I tried.
Cheers,
- Stuart

> -----Original Message-----
> From: Tim Finch, FosterFinch Ltd [mailto:tim@fosterfinch.co.uk]
> Sent: 25 February 2002 18:56
>
>
> ### PSQL
>
> I noticed a thread a few weeks ago about psql in 7.2 in
> cygwin doing a
> segmentation dump.
> I have the same problem.
> I followed the thread that said the 7.1.3 psql build does not
> do the dump.
> It does on mine, giving the same dump.
> I have the postmaster 7.2.2 installed as a service and
> working fine with
> pgAdmin II 1.2.0 (well as far as I can tell).
>
> I did have 7.1.3 installed in Cygwin before putting on 7.2.2
>
> 7.1.3 psql gives this stackdump text file, seemingly the same
> error then
> that psql 7.2.2 gives???
> I am not a C or 'internals of Unix' programmer but have a
> pretty good grasp
> of generally whats going on, but obviously am at a dead end
> myself now. If
> anyone can offer help that would be great. Thanks in advance.
>
> Exception: STATUS_ACCESS_VIOLATION at eip=6108D4A4
> eax=10040412 ebx=10040412 ecx=0000006D edx=00000000
> esi=0241FC98 edi=10040412
> ebp=0241FC14 esp=0241FC08 program=C:\cygwin\bin\psql.exe
> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
> Stack trace:
> Frame     Function  Args
> 0241FC14  6108D4A4  (10040412, 00000000, 0000006D, 61033C93)
> 0241FC54  61033CB4  (00000003, 10040410, 0241FC98, 610529AF)
> 0241FDD4  6798287D  (100403D0, 00000001, 100403D0, 6798319F)
> 0241FE04  67982549  (100403D0, 0040CD7F, 0241FE44, 67981C70)
> 0241FE44  67981EE5  (00000000, 00000000, 00000000, 00000000)
> 0241FEB4  0040D1C9  (00000002, 615624B0, 10040278, 00000000)
> 0241FF10  61003F8E  (00000000, 00000000, 0A01FA30, C0504D3C)
> 0241FF40  61004282  (0040CF38, 0A01FA30, 843696E0, F5CD3C70)
> 0241FF60  610042C1  (00000000, 00000000, 84369870, 00000005)
> 0241FF90  004191E3  (0040CF38, FFFFFFFF, 80430D77, 00000000)
> 0241FFC0  0040103D  (0A01FA30, 0022F7E8, 7FFDF000, 00000000)
> 0241FFF0  77E97D08  (00401000, 00000000, 000000C8, 00000100)
> End of stack trace
>
> ### CREATELANG
>
> I also had trouble running createlang. After creating a
> database using the
> pgAdmin II interface, I tried
> createlang plpgsql databasename
> and I get
>
> Signal 11
> createlang: external error
>
> I was working fine with everything in 7.1.3 in cygwin, all
> the troubles
> have started since putting 7.2.2 on.
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

Re: psql 7.2 AND 7.1.3 failing on Cygwin 1.3.9 pgsql

From
"Tim Finch, FosterFinch Ltd"
Date:
>seen this myself (mind you I've hardly exhaustively tested).
>Either way the problem that was causing psql 7.2 to fail for me has been
>fixed in the last DLL snapshot I tried.
>Cheers,

Well i extracted the psql 7.1.3 executable from the bz2 file and renamed
the 7.2 version to psql72.exe so I guess it was the 7.1.3 that I was running.

Are you talking about the cygwin1.dll? Which version specifically?
I'm new to cygwin, where do I get it from specifically? Is it a special
option in the cygwin windows installer (which I have to say is pretty neat?

Thank you for getting back to me so quickly on this one, very much appreciated

Tim.