Hello there again.
Is there anything one can do about changing debugger behaviour?
When I debug a plpgsql functions that consists of more than one screen
of source code, the debugger shows annoying behaviour ;-)
- as I reach the bottom line of the view area of code debugged (i.e.
running step b
2011/1/20 Ashesh Vashi
> If you're getting this error on windows.
> That's because - the installer did not copy the file in PostgreSQL
> distribution directory because of the build script bug, which is (I think)
> now resolved upstream.
> Please copy the attached file in \include\server\parser\
If you're getting this error on windows.
That's because - the installer did not copy the file in PostgreSQL
distribution directory because of the build script bug, which is (I think)
now resolved upstream.
Please copy the attached file in \include\server\parser\kwlist.h
directory.
(FYI - this is t
Just to let you know, I just did a git pull and found myself staring at the
following error message (after a number of lines of build output):
./db/keywords.c:33:34: error: server/parser/kwlist.h: No such file or
directory
¿missing commit perhaps?
Hi,
Le 20/01/2011 09:42, Piotr Czekalski a écrit :
> [...]
> It seems like there is a minor bug in tree refresh (PgAdmin 1.12.1 and
> earlier) when working on PL/PGSQL functions.
> The client OS is Win 7 x64 Ultimate, server 8.4 running Fedora 12 x86_64
> and 9.0.1 running W2K8R2.
>
> When one ch
Hello PgAdmin Team and Users,
It seems like there is a minor bug in tree refresh (PgAdmin 1.12.1 and
earlier) when working on PL/PGSQL functions.
The client OS is Win 7 x64 Ultimate, server 8.4 running Fedora 12 x86_64
and 9.0.1 running W2K8R2.
When one changes function arguments and/or resul
