On 12.11.2012 17:52, Alvaro Herrera wrote:
Hopefully you noticed that contrib is broken.
Oops.. fixed.
- Heikki
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Heikki Linnakangas wrote:
> On 10.11.2012 11:46, Chen Huajun wrote:
> >>Unfortunately not all compilers support varargs macros. I bumped into
> >>this in February, see
> >>http://archives.postgresql.org/message-id/4f3b72e0.8040...@enterprisedb.com.
> >>My last attempt to fix this was
> >>at http://
On 10.11.2012 11:46, Chen Huajun wrote:
Unfortunately not all compilers support varargs macros. I bumped into
this in February, see
http://archives.postgresql.org/message-id/4f3b72e0.8040...@enterprisedb.com.
My last attempt to fix this was
at http://archives.postgresql.org/pgsql-hackers/2012-04/
Heikki
Unfortunately not all compilers support varargs macros. I bumped into this in
February, see
http://archives.postgresql.org/message-id/4f3b72e0.8040...@enterprisedb.com. My
last attempt to fix this was
at http://archives.postgresql.org/pgsql-hackers/2012-04/msg00812.php. That
patch is
On 08.11.2012 07:59, Chen Huajun wrote:
I am sending patch for errcontext() function.
I use procedural languages to do some operation, but when error occurs
,the CONTEXT error messages from procedural languages doesn't display in
local language.
for example:
Hello,
I am sending patch for errcontext() function.
I use procedural languages to do some operation, but when error occurs
,the CONTEXT error messages from procedural languages doesn't display in
local language.
for example:
postgres=# CR
